JMeter Distributed Testing Step-by-step

This short tutorial explains how to use multiple systems to perform stress testing. Before we start, there are a couple of things to check.

1. The firewalls on the systems are turned off.
2. All the clients are on the same subnet.
3. The server is in the same subnet, if 192.x.x.x or 10.x.x.x ip addresses are used. If the server doesn’t use 192 or 10 ip address, there shouldn’t be any problems.
4. Make sure JMeter can access the server.
5. Make sure you use the same version of JMeter on all the systems. Mixing versions may not work correctly.

Once you’ve made sure that the systems are ready, it’s time to setup remote testing. The tutorial assumes you already have JMeter installed on all of the systems. The way JMeter works is 1 master controller initiates the test on multiple slave systems.

Terminology

Before we dive into the step-by-step instructions, it’s a good idea to define the terms and make sure the definition is clear.

Master — the system running JMeter GUI, which controls the test

Slave — the system running JMeter-server, which takes commands from the GUI and send requests to the target system(s)

Target — the webserver we plan to stress test 1/4

Step-by-Step

1. On the slave systems, go to JMeter/bin directory and execute JMeter-server.bat (JMeter-server on unix). On windows, you should see a dos window appear with “jre\[version]\bin\rmiregistry.exe”. If this doesn’t happen, it means either the environment settings are not right, or there are multiple JRE installed on the system. Note: [version] would be the jre version installed on the system.

• Open JMeter-server.bat in a text editor
• go to line 47 and find “:setCP”
• edit “START rmiregistry” to the full path. Example: “START C:\\jre\bin\rmiregistry”

2. On master system acting as the console, open windows explorer and go to JMeter/bin directory

3. open JMeter.properties in a text editor

4. edit the line “remote_hosts=127.0.0.1”

5. add the IP address. For example, if I have JMeter server running on 192.168.0.10, 11, 12, 13, and 14, the entry would like like this: remote_hosts=192.168.0.10,192.168.0.11,192.168.0.12,192.168.0.13,192.168.0.14

6. Start JMeter.

7. Open the test plan you want to use

Starting the Test

At this point, you are ready to start load testing. If you want to double check the slave systems are working, open JMeter.log in notepad. You should see the following in the log.

JMeter.engine.RemoteJMeterEngineImpl: Starting backing engine

If you do not see this message, it means JMeter-server did not start correctly. For tips on debugging the issue, go to the tips section. There are two ways to initiate the test: a single system and all systems.

Start a single clients

1. click Run at the top
2. select Remote start
3. select the IP address

Start all clients

1. click Run at the top
2. select Remote start all or use CRTL-Z

Limitations

1. There are some basic limitations for distributed testing. Here’s the list of the known items in no specific order.
2. RMI cannot communicate across subnets without a proxy; therefore neither can JMeter without a proxy.
3. Since JMeter sends all the test results to the controlling console, it is easy to saturate the network IO. It is a good idea to use the simple data writer to save the results and view the file later with one of the graph listeners.
4. Unless the server is a large multi processor system, in most cases 1–2 clients is sufficient to overwhelm the server.
5. A single JMeter client running on a 2–3Ghz CPU (recent cpu) can handle 300–600 threads depending on the type of test. (The exception is the webservices). XML processing is CPU intensive and will rapidly consume all the CPU cycles. As a general rule, the performance of XML centric applications will perform 4–10 slower than applications using binary protocols.

Additional resources

http://wiki.apache.org/JMeter/JMeterFAQ#How_to_do_remote_testing_the_.27proper_way.27.3F

http://JMeter.apache.org/usermanual/remote-test.html

Tips

In some cases, the firewall may still be blocking RMI traffic. Symantec Anti Virus and Firewall

In some cases, Symantec firewall needs to be stopped from windows services.

1. open control panel
2. open administrative tools
3. double click services
4. Go to down to symantec anti virus, right click and select stop

Windows firewall

1. open network connections
2. select the network connection
3. right click and select properties
4. select advanced tab
5. uncheck internet connection firewall

Linux

On Suse linux, ipchains is turned on by default. For instructions, please refer to the “remote testing” in the user manual.

On RedHat (or derivatives), iptables (netfilter) is turned on by default. Execute “service iptables stop” to stop the Linux netfilter firewall.

Check out Loadium blog for more!