background image
<< Index | Step-by-Step Setting up Slaves and Master >>

JMeter Distributed Testing Step-by-step

<< Index | Step-by-Step Setting up Slaves and Master >>
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 the systems are ready, it's time to setup remote testing. The tutorial
assumes you already have JMeter installed on all the systems. The way JMeter works is 1 master
controller initiates the test on multiple slave systems.
Diagram 1
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