Performance Testing using JMeter

Overview

Performance testing is one of the most important stages of any product launch to confirm and validate the product’s performance. It describes putting a program or software through a particular workload and seeing how it performs. It looks for unexpected behavior from the application or sees if it operates as expected under that load.

Introduction

Performance testing tests the system’s responsiveness, speed, dependability, and resource utilization. Performance testing seeks to find and remove any obstacles to the software program.

A software program’s three primary components are the main focus of performance testing:

• Scalability – The maximum user load is established
• Stability – The application is tested under various loads
• Speed – The program’s reaction speed

Why JMeter?

Let’s examine these six factors to see why JMeter is the most widely used performance testing tool:
1. No Charge
JMeter lets users automate tasks, provides an easy-to-use interface, and is free of cost.
2. Application Performance Testing
JMeter aids in the performance testing of both static and dynamic resources. AJAX, Servlets, JSP, other dynamic resources, and HTML and JavaScript are static resources.
3. Stress testing and load testing
Stress and load testing are two types of performance testing that JMeter offers. As a result, it indicates the server can support the highest number of concurrent users.
4. Framework
JMeter’s framework supports multi-threading, enabling multiple thread groups to do concurrent and simultaneous sampling.

5. Visual Evaluation
   JMeter makes the analysis readable and engaging by enabling the performance testing representation in a graphical format such as a graph, tree, table, report, etc.
   6. Independent of Platform
   JMeter can execute a Java Virtual Machine on any platform or server because it is fully Java-based.

Demo: JMeter Performance Testing

Prerequisites to install JMeter

• Java needs to be installed in your system

Extract J meter -> Go to folder -> Bin -> J meter

Two Types of Running J Meter

1. GUI mode
2. Non-GUI mode

Further Non- Gui mode is two types-

• J meter running in server mode
• J meter running in command line

Limitations

J meter in GUI mode is limited as it slows down the CPU utilization while running the recorded script. It is perfect for adding and editing configurations like no threads and samplers, which you can view without listeners helping in debugging.

Steps to perform performance test

1. Select the jmeter.bat file and double click on it.

Test plan is a place or container where all elements used to perform the test will be stored. All the requests, listeners, and everything are stored here.

2. Rename the Test plan as J-meter

3. Right click on the test file -> select add -> Thread -> choose thread group -> define configuration as per requirement

Thread group– thread groups refer to the users that are used, created, or needed to run this test.

4. Define no of threads and no of ramp-up count

Ramp- up time – the period that states the time gap between the users hits

Loop count– where we can choose how many times the test will run for the number of users. It can be chosen for infinite numbers of run

5. Define the config for HTTP request configuration

6. Right click on the Test plan named j-meter -> click on add -> listeners -> and choose the required metrics.

7. Let’s do it again for 10 threads(users) with a 10 loop count, which means for each user, the test will run for 10 times

8. Report

This is how we can check performance tests using J-meter.

How to aggregate the results?

Create the 03 different HTTP requests as a Sampler of which you want to aggregate the results:

Thread -> Add -> Listener -> Aggregate report -> Run

Aggregated Results:

Conclusion

Drop a query if you have any questions regarding JMeter and we will get back to you quickly.

About CloudThat