Skip to main content

How to analyze a JMeter summary report?

 

A Jmeter Test Plan must have listener to showcase the result of performance test execution.

  • Listeners capture the response coming back from Server while Jmeter runs and showcase in the form of – tree, tables, graphs and log files.

  • It also allows you to save the result in a file for future reference. There are many types of listeners Jmeter provides. Some of them are: Summary Report, Aggregate Report, Aggregate Graph, View Results Tree, View Results in Table etc.

Here is the detailed understanding of each parameter in Summary report.

By referring to the figure:


Label: It is the name/URL for the specific HTTP(s) Request. If you have selected “Include group name in label?” option then the name of the Thread Group is applied as the prefix to each label.

Samples: This indicates the number of virtual users per request.

Average: It is the average time taken by all the samples to execute specific label. In our case, the average time for Label 1 is 942 milliseconds & total average time is 584 milliseconds.

Min: The shortest time taken by a sample for specific label. If we look at Min value for Label 1 then, out of 20 samples shortest response time one of the sample had was 584 milliseconds.

Max: The longest time taken by a sample for specific label. If we look at Max value for Label 1 then, out of 20 samples longest response time one of the sample had was 2867 milliseconds.

Std. Dev.: This shows the set of exceptional cases which were deviating from the average value of sample response time. The lesser this value more consistent the data. Standard deviation should be less than or equal to half of the average time for a label.

Error%: Percentage of Failed requests per Label.

Throughput: Throughput is the number of request that are processed per time unit(seconds, minutes, hours) by the server. This time is calculated from the start of first sample to the end of the last sample. Larger throughput is better.

endTime = lastSampleStartTime + lastSampleLoadTime
startTime = firstSampleStartTime
converstion = unit time conversion value
Throughput = Numrequests / ((endTime - startTime)*conversion)

KB/Sec: This indicates the amount of data downloaded from server during the performance test execution. In short, it is the Throughput measured in Kilobytes per second.

# Avg. Bytes: Avegare of total bytes of data downloaded from server. Totals is average bytes across all samples.

Latency is a difference between time when request was sent and time when response has started to be received.

Response time (= Sample time = Load time = Processing Time + Latency Time) is a difference between time when request was sent and time when response has been fully received.



Labels:

Comments

Post a Comment

Popular posts from this blog

What is usability testing ?

What is usability testing ? Usability testing is a way to see how system is easily usable by the end users. It basically verifies the interface of website and test whether application is user friendly or not. It identifies how the customer will feel comfortable in using the software. Usability Testing not only test Look and feel it also test in how many steps customer will reach their goals Example: Suppose there is an application in which user wants to generate Attendance Report of Employees on daily basis, and user has to follow below steps: 1) Login to Application. 2) Click on Attendance System 3) Click on Reports and select Employee Attendance Report 4) Various Employee Attendance reports will be displayed of different teams. Select particular report(say: Select Team) 5) Select the parameters which you want to display in report say: • Date • Shift Timings • Employee Id • Name • In/Out Time • Status (Present/Absent/leave) 6) Click on Generate Report 7) Click on Print option In this ...
2 comments
Read more

What is Error, Bug and Defec ?

What is Error, Bug and Defect in software testing ? Error :- When developer compile a program and program compilation is failed due to some syntax problem or not used correct logic, is called an Error.  For example:-  public class  { public static void main( string []args) { s.o.p(" hello") } } Now after running this program, we will get an error because there is syntax issues as we haven't use correct syntax to print output. Bug : Bug is something that is not producing expected output or something is not behaving as expected.  For example- Developer develop a program to add two number and that program is running fine but producing wrong result. public class  { public static void main( string []args) { int a=3; int b=2; int s= ++a+b; System.out.println(" hello"); } } Actual output: 6 Expected outpit: 5 So here system is not producing expected output after adding two number. In simple term, whe...
Post a Comment
Read more