Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When timing my (web) application for performance/latency, should I use the minimum time measured in n runs, or the average? Or something else?
If it’s the latter case, when to use what?
If your answer is going to be something along the lines of, “research it, dude”, could you point me to a good resource?
You could retrieve the values, store them by time, with couple (time_of_the_call, response_time). Then you may treat these data with tools, draw graphs, make statistics.
I think an average, minimum, etc, is not sufficient, you need a set of measures.
For example you may put you data in a csv file and import in excel, or even use google graph api to draw real time graphs.