LoadRunner calculates hits per second in the “Hits per second” graph depending on the HTTP requests sent out each second. If there are no HTTP requests sent for some time, then a request is sent out, and the “hits per second” is computed for the entire interval since the last hit was received.
The measurement seen on the graph is per second, but the granularity of the graph is not 1 second. It is possible to have fractions of hits per second. If you change the granularity to 1 second, then only whole hits per second will be displayed.
Say you have only one HTTP Request that is sent at the fifth second of a scenario before which there are no requests sent, the hits per second would be recorded as 0.2 hits per second (HPS) for each of the first 5 seconds. If, after that, you have 1 hit every 1 second for the next 5 seconds they would be displayed as 1 HPS for the next 5 seconds in the HPS graph.
The Average HPS however will be different as follows
2/6 = 0.33 HPS for the 6th second
4/8 = 0.50 HPS for the 8th second
6/10= 0.60 HPS for the 10th second
If, after that, if there is no HTTP request sent for the next 4 seconds and ONLY one HTTP request is sent at the fifth second, the HPS would be 0.2 for the last 5 seconds.
Clear as mud?
Did you enjoy this article? Help spread the word by sharing:
Engage in the conversation and leave a comment:
About Scott Moore (153 articles)
With over 20 years of IT experience with various platforms and technologies, Scott has tested some of the largest applications and infrastructures in the world. He is a Certified Instructor and Certified Product Consultant in HP’s LoadRunner and Performance Center products. He currently holds HP certifications for ASE, ASC, and CI. A thought leader in the APM space, he speaks regularly at IT conferences and events