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 Create a New Test under Performance Testing.


Step 2: After selecting the button “Create Test” configure the provided steps in that you create.



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




  • Total Users : 100 (Number of users who connect to the target website: 100)
  • Duration (min): 15 (Number of time to execute testing)
  • Ramp-Up Time : 15 minutes

The Thread Count and The Loop count 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 per 100 users)

Once configuration details are entered and verified, click the “Run Test” button on the same screen.

After clicking “Run Test,” you will see the following configurations and the “Launch Servers” button, which will start performance tests.



After successfully running your load test, navigate to the build reports dashboard.


Step 3: After selecting your ​’Runs Tests​’ Verify the JMeter Performance Dashboard.




Inspect CPU usage:
Monitor your app’s CPU consumption for spikes or prolonged excessive usage. Compare app CPU usage against system CPU usage and ensure your app doesn’t degrade device performance.

Manage memory usage:
Find out precisely how much memory your app consumes. Compare system memory used, system memory available, and your app’s memory usage. Detect memory leaks in advance and prevent app crashes.

Analyze battery usage:
Narrow down on tasks that consume too much battery power or cause battery drain. Check device temperature and battery charge percentage to ensure apps consume only the optimal amount of battery power—and no more.

Examine bandwidth consumption :
Check bandwidth consumption during runtime and inactivity. Monitor upload and download speeds. Achieve maximum efficiency by identifying and eliminating bandwidth bottlenecks.


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 helpful.

Table of Contents