Bobcares

Distributed Testing in JMeter non-GUI mode | Guide

by | Sep 3, 2023

Learn more about Distributed Testing in JMeter non-GUI mode from our experts. Our Server Management Support team is here to help you with your questions and concerns.

Distributed testing in JMeter in non GUI mode

Did you know that Distributed load testing in JMeter involves using multiple JMeter instances running on different machines to simulate a higher load on our application?

JMeter allows us to perform distributed testing in non-GUI mode. In other words, we can run the test without the graphical user interface.

Distributed Testing in JMeter non-GUI mode

Furthermore, this method is more efficient and suitable for large-scale testing.

Let’s take a look at how to perform distributed testing in JMeter’s non-GUI mode.

How to perform Distributed Testing in JMeter non-GUI mode

  1. First, we have to create our JMeter test plan normally and specify the test scenarios, thread groups, samplers, listeners, etc.
  2. Then, we have to copy our JMeter test plan to all the machines that will act as JMeter “slave” instances. Furthermore, these machines will contribute to generating load for our distributed test.
  3. Next, we have to choose one machine to act as the JMeter “master.” This machine is responsible for coordinating the test execution and collecting results. The other machines will be our “slaves.”
  4. Then, we have to open a terminal and head to JMeter’s bin directory on the master machine.
    We can use this command to start the test in non-GUI mode:

    jmeter -n -t path_to_test_plan.jmx -R slave1_IP,slave2_IP,... -l test_results.jtl

    Here:

    • -n: Starts JMeter in non-GUI mode.
    • -t path_to_test_plan.jmx: The path to our test plan.
    • -R slave1_IP,slave2_IP,…: Lists the IP addresses or hostnames of the slave machines.
    • -l test_results.jtl: The name of the results file.
  5. Now, we can run JMeter in non-GUI mode on each slave machine with this command:

    jmeter -s -j jmeter_slave.log

    Here:

    • -s: Starts JMeter in server mode on the slave machine.
    • -j jmeter_slave.log: The name of the log file.
  6. Then, the master machine will coordinate the distribution of load to the slave machines. We have to monitor the terminal on the master and slaves for any output or errors.
  7. Now, it is time to analyze the results using JMeter’s listeners. Alternatively, we can load the generated .jtl results file into the GUI for analysis.

Benefits of Distributed Testing in Non-GUI Mode

 

  • Efficient resource utilization:

    Running tests in non-GUI mode consumes fewer resources compared to the GUI mode.

  • Scalability:

    We can easily scale our testing by adding more slave machines to distribute the load.

  • Automation:

    Non-GUI mode is suitable for automation and integration into CI/CD pipelines.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Techs demonstrated how to carry out Distributed testing in JMeter in non GUI mode.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF