1. The need to look at adding a listener called summary report, and after the finish
Label: sampler / listener name
Samples: number of transactions
Average: The average time to complete a transaction consumed (average response time)
Median: all intermediate values of the response time, i.e. 50% of the user response time, probably mean
Min: minimum response time
Max: Maximum response time
More units are in ms
Std.Dev: standard deviation, the smaller the more stable
Error%: Transaction error rate
Throughtput: the number of transactions per second, ie tps, the bigger the better
KB / sec: network throughput
When the results of performance analysis, we generally will Aggregate Report data concern more, such as: Average, 90% Line, Min, Max, Error%, Throughput, in the Summary Report will also focus Std Dev..
(Standard deviation of the response time), if the value is large, so little reference value Min and Max, while 90% Line (90% request response time) is an important performance indicators.
Then Error% value, preferably not more than 1%, otherwise the system performance indicates that too much pressure. Throughput can be understood as TPS (Transaction per Second) the bigger the better.
Note, Aggregate Report and Summary Report operating results are cumulative, so before each test run, first empty the last run results.
Label request is the name of the sampler, the Sampler HTTP request which added the controller and checking the transaction Generate parent sample, the Report only one row becomes the Label Record (Label name of the transaction controller)
Further, the JMeter Aggregate Graph is also provided to graphically view data, intuitive, easy to analyze performance results.
Save the file Address