How to Setup Apache JMeter to Perform a Stress Test on Linux Server

Apache JMeter is a powerful open-source tool designed for load testing web applications and other services. By simulating multiple users sending requests to a web server, JMeter helps administrators and developers understand how their server reacts under heavy load.

This is crucial for ensuring that your server can handle real-world traffic and provide a smooth user experience.

In this tutorial, we will guide you through the process of setting up JMeter on Linux distributions, specifically Ubuntu and CentOS, and then using it to perform a stress test.

Let’s get started.

Step 1. Installing Java

Before installing JMeter, ensure that Java is installed on your system, as JMeter requires it to run.

Ubuntu:

sudo apt update
sudo apt install openjdk-11-jdk

CentOS:

sudo yum update
sudo yum install java-11-openjdk

Step 2. Downloading and Installing JMeter

Ubuntu:

wget https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.4.1.tgz
tar -xvzf apache-jmeter-5.4.1.tgz

CentOS:

wget https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.4.1.tgz
tar -xvzf apache-jmeter-5.4.1.tgz

Download latest release: https://jmeter.apache.org/download_jmeter.cgi

Step 3. Launching JMeter

Navigate to the JMeter bin directory and start JMeter:

cd apache-jmeter-5.4.1/bin
./jmeter

Step 4. Setting Up a Test Plan

A test plan in JMeter describes a series of steps JMeter will execute when run. It’s the foundational element of any JMeter test. Here’s a more detailed breakdown:

1. Open JMeter: Launch the JMeter application. You’ll be greeted with a GUI that has a tree structure on the left side. This tree will house all the elements of your test.
2. Creating a New Test Plan: By default, a new test plan is already created. Right-click on the “Test Plan” node.
3. Add a Thread Group: The Thread Group is the beginning point of your test plan. It simulates user requests to the server:
   • Right-click on the Test Plan.
   • Navigate to Add > Threads (Users) > Thread Group.
4. Configuring the Thread Group:
   • Number of Threads (Users): This represents the number of users you want to simulate. For instance, setting it to 100 means 100 virtual users will be sending requests to your server.
   • Loop Count: Determines how many times the test will be executed. Setting it to 10 with 100 users means 1000 requests will be sent.
   • Ramp-Up Period: The time (in seconds) taken to get all the threads started. If you have 100 users and a ramp-up period of 100 seconds, JMeter will take 100 seconds to get all 100 threads up and running.
5. Adding an HTTP Request:
   • Right-click on the Thread Group.
   • Navigate to Add > Sampler > HTTP Request.
   • In the HTTP Request form:
     • Server Name or IP: Enter the domain name or IP address of your server.
     • Port Number: Typically, for HTTP it’s 80 and for HTTPS it’s 443, but it could be different based on your setup.
     • Path: The endpoint of your application you want to test, like “/home” or “/login”.

Step 5. Adding Listeners

Listeners are JMeter’s way of providing visual feedback. They capture the data from test execution and represent that data in various ways:

1. Adding a Listener:
   • Right-click on the Thread Group.
   • Navigate to Add > Listener.
2. Popular Listeners:
   • View Results in Table: This listener provides a tabular view of all the requests sent during the test. It displays the status, response time, and other vital metrics for each request.
   • Graph Results: It provides a visual representation of the test results. You can see how response times varied over the course of the test, giving insights into potential bottlenecks.

Step 6. Running the Test

After setting up the test plan and adding listeners, you’re ready to execute the test:

1. Starting the Test: At the top of the JMeter GUI, you’ll see a green “Run” button (it looks like a play button). Click on it to start the test.
2. Monitoring the Test: As the test runs, the listeners you added will begin populating with data. You can monitor these in real-time:
   • For the “View Results in Table” listener, you’ll see each request being logged.
   • The “Graph Results” listener will plot response times as the test progresses.
3. Stopping the Test: If you need to halt the test for any reason, click the red “Stop” button (it looks like a stop sign) at the top of the GUI.

Remember, while JMeter provides valuable insights through its GUI, for more extensive tests, it’s recommended to run JMeter in non-GUI mode to conserve resources.

Running JMeter in Non-GUI Mode

Running JMeter in non-GUI mode is essential when conducting large-scale performance tests. The GUI consumes significant resources, which can skew test results. Non-GUI mode allows JMeter to use all available resources for the test itself, ensuring more accurate results. Here’s a step-by-step guide:

1. Creating Your Test Plan in GUI Mode

Before you can run a test in non-GUI mode, you need to create and save it:

1. Launch JMeter in GUI mode.
2. Set up your test plan as required.
3. Save the test plan by navigating to File > Save Test Plan as. Save it with a .jmx extension, for example, my_test_plan.jmx.

2. Running the Test in Non-GUI Mode

1. Open Terminal or Command Prompt: Navigate to the directory where JMeter is installed.
2. Execute the Test: Use the following command structure to run your test:

./jmeter -n -t [path-to-test-plan] -l [path-to-result-file]

For example:

./jmeter -n -t /path/to/your/testplan/my_test_plan.jmx -l /path/to/results/results.jtl

Here’s a breakdown of the command:

• -n: This flag indicates you are running JMeter in non-GUI mode.
• -t: Specifies the path to your JMeter test plan.
• -l: Specifies the path where the results will be saved.

3. Monitoring the Test

While you won’t have the JMeter GUI to monitor in real-time, you can still keep an eye on server metrics using tools like htop (for CPU and memory usage) or nmon (for a more comprehensive view including network and disk I/O).

4. Analyzing the Results

After the test completes, JMeter will save the results to the specified .jtl file. You can then:

1. Open the Results in JMeter GUI: Launch JMeter in GUI mode, add a listener like “View Results in Table” or “Summary Report”, and then load the .jtl file to view and analyze the results.
2. Use Third-party Tools: There are tools and platforms, like Grafana combined with InfluxDB, that can visualize JMeter results for deeper analysis.

5. Additional Tips

• Log File: By default, JMeter logs messages in the jmeter.log file. It’s a good practice to check this file for any warnings or errors after your test.
• Adjust Heap Size: For large tests, you might need to increase the Java heap size to prevent memory issues. This can be done by editing the jmeter startup script.
• Use Plugins: Even in non-GUI mode, JMeter plugins can enhance your testing. For instance, the Concurrency Thread Group and Stepping Thread Group can offer more advanced ramp-up patterns.

Commands Mentioned

• sudo apt update – Updates the package list for upgrades on Ubuntu.
• sudo yum update – Updates the package list for upgrades on CentOS.
• wget [URL] – Downloads files from the internet.
• tar -xvzf [FILENAME] – Extracts a tarball file.

Additional Tips

• Regularly Update JMeter: Ensure that you are using the latest version of JMeter to benefit from the latest features and security patches.
• Use Plugins: JMeter has a rich ecosystem of plugins that can enhance its capabilities. Consider exploring the JMeter Plugin Manager to find tools that can aid your testing process.
• Monitor Server Health: While running stress tests, it’s also beneficial to monitor the health of your server using tools like htop (an interactive process viewer for Unix systems) or nmon (A system monitor tool for Linux, which shows usage for CPU, memory, network, disks, and more.). This gives you a holistic view of how the server is handling the load.
• Distributed Testing: For extremely high loads, consider using JMeter’s distributed testing feature. This allows you to run tests from multiple machines, simulating an even larger number of users.
• Documentation: The official JMeter documentation is a valuable resource. It provides in-depth information on every feature and can help troubleshoot any issues you might encounter.

FAQ

1. What is Apache JMeter used for?

   Apache JMeter is an open-source tool designed for load testing web applications and other services. It simulates multiple users sending requests to a server, helping to understand the server’s performance under heavy load.

2. Why is Java required for JMeter?

   JMeter is a Java-based application, and thus, it requires Java to run. The Java Runtime Environment (JRE) provides the libraries and components needed for JMeter to function properly.

3. How do I view the results of my JMeter test?

   In JMeter, you can view test results using listeners. Popular listeners include “View Results in Table”, “Graph Results”, and “Summary Report”. These listeners provide detailed insights into the test’s performance metrics.

4. Can JMeter be used for testing non-web applications?

   Yes, while JMeter is popularly used for web application testing, it can also test various other services like FTP, LDAP, and databases. It’s a versatile tool suitable for various testing scenarios.

5. Is JMeter suitable for large-scale load testing?

   Yes, JMeter can handle large-scale load testing. However, for very high loads, it’s recommended to distribute the testing across multiple machines using JMeter’s distributed testing capabilities.

6. How can I extend JMeter’s capabilities?

   JMeter’s capabilities can be extended using plugins. The JMeter Plugin Manager offers a variety of plugins that can introduce new samplers, listeners, and other functionalities to enhance your testing process.

7. What are the alternatives to JMeter for load testing?

   While JMeter is a popular choice, there are other load testing tools like LoadRunner, Gatling, and Locust that are also widely used in the industry. Each tool has its strengths and is suited for different scenarios and requirements.

Conclusion

Understanding how your server reacts under heavy load is crucial for ensuring optimal performance and a seamless user experience. Apache JMeter provides a comprehensive solution for simulating real-world traffic and stress-testing your server.

Running JMeter in non-GUI mode is crucial for large-scale and resource-intensive tests. It ensures that the tool uses all available resources for the test, providing more accurate and reliable results. By following the steps above, you can efficiently execute and analyze your performance tests without the overhead of the GUI.

By following this tutorial, you’ve learned how to set up JMeter on Linux distributions, specifically Ubuntu and CentOS, and use it effectively.

For a deeper dive into web servers, you can explore the best web server software or learn more about individual servers like Apache, Nginx, and LiteSpeed.

For further insights into hosting solutions, explore dedicated server, VPS server, cloud hosting, and shared hosting options.

Welcome to the comments.