Distributed Mode in JMeter

Distributed testing enables having a local JMeter (master) that handles the test execution, together with multiple remote JMeter instances (slaves) that will send the request to our target server.

  • There are some limitations if you're running your load test in your own machine.
  • Distributed Testing is a kind of testing that uses multiple systems to perform Stress Testing.
  • Distributed testing is applied for testing websites and server applications when they are working with multiple clients simultaneously.

Example: If you want to run the Load Test in JMeter of 5000 users, with the limited memory configuration and RAM Configuration. After some user's execution, your local system will not support the further execution of 5000 Users.

If you still try to execute the 5000 Users, then you will get the wrong Outputs. That's why it is not recommended to use 5000 users on a single machine.

The Architecture of JMeter Distributed Mode

Distributed testing enables having a local JMeter (master) that handles the test execution, together with multiple remote JMeter instances (slaves) that will send the request to our target server.

But before being able to run JMeter in a distributed way, there are a couple of simple steps you must perform.

First, we need to have multiple computers.

Then we need to get the JMeter Server running on each slave system that we have. For that purpose, we have to execute the jmeter-server.bat (jmeter-server for Unix users) that is located in the jmeter/bin. Once we run it we should see something like this:

Distributes Testing uses the Client-Server Model as the Figure below :

client-server-model-jmeter
  • Master : The system running JMeter GUI, control each slave.
  • Slave : The system running JMeter-server, receives a command from the master and sends a request to a server under test.
  • Target : The web server under test, gets a request from slaves.
0 results
Comment / Suggestion Section
Point our Mistakes and Post Your Suggestions