Performance & Load Testing using JMeter in TestGrid

You are here:
< All Topics

JMeter Load Testing

An open-source desktop application based on Java called Apache JMeter is a load testing tool that is used in the JMeter Load Testing process. A key tool for determining whether or not the web application under test can handle high load requirements is load testing with JMeter. Analyzing the entire server while it is under heavy load is also helpful.


Performance testing with JMeter

JMeter Performance Testing is a testing technique that evaluates a web application’s performance using Apache JMeter. JMeter for performance testing offers a variety of graphical analysis tools, assists in finding concurrent users on a website, and aids in testing both static and dynamic resources. Web applications are subjected to load testing and stress testing as part of JMeter performance testing.


Apache JMeter testing tool offers following benefit in Performance testing:

  • JMeter can be used to test the performance of both static and dynamic resources, including JSP, Servlets, and AJAX as well as Java, JavaScript, and HTML.
  • JMeter can figure out how many concurrent users your website can support.
  • JMeter offers numerous graphical performance report analyses.


Load testing: Simulating multiple concurrent users accessing Web services to model the expected usage.

Stress testing: Each web server has a maximum load limit. When the load exceeds the limit, the web server begins to respond slowly and starts making mistakes. Stress testing is done to determine the maximum load that a web server can support.


Step1: Log in using your TestGrid credentials, then select the ‘Performance Testing’ option under Dashboard.

After clicking, navigate to the Run Load Test option under Performance Testing.

Step2: After selecting “Run Load Test,” Configure the provided steps in a “New Load Test” that you create.

– Uploading any sample.jmx file. Here, start the configuration as you need it.



  • Number of Threads: 100 (Number of users connects to the target website: 100)
  • Loop Count: 10 (Number of time to execute testing)
  • Ramp-Up Period: 100

The Thread Count and The Loop Counts are different.

Ramp-Up Period tells JMeter how long to delay before starting the next user. For example, if we have 100 users and a 100-second Ramp-Up period, then the delay between starting users would be 1 second (100 seconds /100 users)





Once Configuration details are entered and verify, the to start “Load run test” button on same screen.



You can check the logs as “Dashboard generated” once the load test run is complete.


After click “Report” option on left panel side.

Step3: After selecting ​’Report​’ Verify the JMeter Performance Dashboard.


NOTE: The above values depend on several factors like current server load at Google, your internet speed, your CPU power etc. Hence, it’s very unlikely that you will get the same results as above. So don’t panic! If you’re interested in understanding how server load impacts performance and how to test it, you might find this load testing.

Table of Contents