Load Testing with JMeter and JMeter Plugins- PerfMon Server Agent

By using the JMeter and JMeter Plugins, we test the load of the application step by step.

Plugins for JMeter-

Jmeter Has the following plugins as Standard Set, PerfMon Agent to use with Standard Set, Extras Set, Extras with Libs Set, WebDriver Set, Hadoop Set.

Basically, the JP@GC set contains two types of plugins: graph plugins and JMeter functionality extensions.

  • Download the JMeter Plugin from the Jmeter. 
  • After Downloading the extract the zip file.
  • Copy the library of the plugins and paste into the JMeter – lib>ext>paste .
  • Now Start the server Agent by click on the startAgent.

Start 0

Plugin 01

Let’s move on…..

1. Add the Thread Group-

Test_Plan.1

Add Thread 2

  • Number of Threads: 50 (Number of users to hit on website)
  • Ramp-Up Period: 50 (After 1 sec next user is hit on the server)
  • Loop Count: 1 (Number of time to execute this plan)

Thread Group 22. Add the Http Request-

  • Right-click on Thread Group> Add >Sampler> HTTP Request
  • Now enter the url on which page you want to test the load. 

Http Request 3

3. Add the Listener:

  • To show the Result in the table and graph format we use the listener.
  • Right-click on Thread Group> Add >Listener>……..

Listener 4

4. After adding the listener now save the test plan. Click on the start button to test the load on the application.

5. After completing the Test, you can see the result in the below graph and report.what is the status of our application.

6. Aggregate Report-

Here you can see the report of the tested application.

Aggregate Report

7. Aggregate Graph-

Aggregate Graph

8. Summary Report-

Summary Report

Label – The label of the sample.
Samples – The number of samples with the same label
Average – The average time of a set of results
Median – The Median is the time in the middle of a set of results. 50% of the samples took no more than this time; the remainder took at least as long.
90% Line – 90% of the samples took no more than this time. The remaining samples at least as long as this. (90 th percentile)
Min – The shortest time for the samples
Max – The longest time for the samples
Error % – Percent of requests with errors

Throughput – the Throughput is measured in requests per second/minute/hour. The time unit is chosen so that the displayed rate is at least 1.0. When the throughput is saved to a CSV file, it is expressed in requests/second, i.e. 30.0 requests/minute is saved as 0.5.

Kb/sec – The throughput measured in Kilobytes per second

9. View Result Tree –

View Results Tree

10. View Result in Table-

View Results in Table

11. Graph Result-

Graph Results

Data – plot the actual data values
Average – plot the Average
Median – plot the Median (midway value)
Deviation – plot the Standard Deviation (a measure of the variation)
Throughput – plot the number of samples per unit of time

Black: The total number of current samples sent.
Blue: The current average of all samples sent.
Red: The current standard deviation.
Green: Throughput rate that represents the number of requests per minute the server handled

To analyze the performance of the web server under test, you should focus on 2 parameters

  • Throughput
  • Deviation

High Throughput: better is the server performance
Low Deviation: better
 is the server performance

12. jp@gc – Active Threads Over Time

It is showing how many active threads are there in each thread group during test run.

jp@gc - Active Threads Over Time

13. jp@gc – Bytes Throughput Over Time

This graph will display the amount of bytes sent and received by JMeter during the load test-

jp@gc - Bytes Throughput Over Time

14. jp@gc – Composite Graph

jp@gc - Composite Graph

15. jp@gc – Hits per Second

This graph shows the number of transactions per second for each sampler. It counts for each seconds the number of finished transactions.

jp@gc - Hits per Second

16. jp@gc – PerfMon Metrics Collector

jp@gc - PerfMon Metrics Collector

17. jp@gc – Response Codes per Second

This graph will display the response code per second returned during the test.

jp@gc - Response Codes per Second

18. jp@gc – Response Latencies Over Time

A latency is the duration between the end of the request and the beginning of the server response.This graph will display the response latencies during the load test-

jp@gc - Response Latencies Over Time

19. jp@gc – Response Times Over Time

This graph will display for each sampler the average response time in milliseconds

jp@gc - Response Times Over Time

20. jp@gc – Response Times vs Threads

This graph shows how Response Time changes with amount of parallel threads. Naturally, server takes longer to respond when a lot of users requests it simultaneously. This graph visualizes such dependencies.

jp@gc - Response Times vs Threads

21. jp@gc – Transactions per Second

This graph shows the number of transactions per second for each sampler. It counts for each seconds the number of finished transactions.

jp@gc - Transactions per Second22. Response Time Graph

Response Time Graph

 

^^^^^^^^^^^^^^^^^^^^^COMPLETED^^^^^^^^^^^^^^^^^^^^^^
Please share your views—

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s