Aggregation reports: Aggregate report
#Samples: Number of requests made. such as the third row record, simulates 20 users, loops 100 times, so displays 2000
Average: Average response time (unit:). The default is the average response time for a single request, and when transaction controller is used, the average response time can also be displayed in transaction units
Median: Median, which is the response time of 50% users
90%line:90% Response time for users
95%line:95% Response time for users
99%line:99% Response time for users
Note: Why you should have *% user response time. Because when evaluating the results of a test, it is not enough to have only average thing response time. If there was a test, a total of 100 requests were responded to, with a minimum response time of 0.02 seconds, a maximum response time of 110 seconds, and an average transaction response time of 4.7 seconds, you would not think whether the minimum and maximum response times so large deviations would result in the average itself being untrustworthy.
We can continue to add 96/97/98/99/99.9/99.99th after the th, and draw a curve with Excel's chart function to show the distribution of system response time more clearly. At this point you may find that the maximum probability of the occurrence is only 1 per thousand or even one out of 10,000, and 99% of the user request response time is defined by the performance requirements of the range, the following figure is the lowest response time of the probability is very small, the actual 99% of the user request response time is 20000 +
Min: Minimum response time
Max: Maximum response time
error%: Number of requests with errors in this test/total number of requests
Throughput: Throughput. By default, the number of requests completed per second (as shown in the figure below)
Kb/sec: The amount of data received from the server side per second.