Distributed execution principle
1. During JMeter distributed testing, select one of the machines as the scheduling machine (master) and the other machines as the execution machine (slave).
2. When executing, the master will send the script to each slave. The slave will start executing it after getting the script. The slave does not need to start the GUI when executing. I understand that it should be executed through the command line mode.
3. After the execution is completed, the slave will send the results back to the master, and the master will collect and summarize all slave information.
Prerequisites:
1. First create a JMeter interface stress test script.
2. The scheduling machine (master) + execution machine (slave) are in the same LAN, and the same version of JMeter + jdk is installed.
Configure the scheduler (master) + execution machine (slave)
Modify the JMeter.properties file in JMeter/bin of the main machine as follows.
Remember to modify: server.rmi.ssi.disable=true, otherwise an error will be reported.
Do a similar configuration on the slave machine.
Before starting JMeter, you must first start JMeter-server, otherwise an error will be reported.
Start JMeter.sh (mac), JMeter.bat (window), execute the script, and run - remote start.
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly:
This information should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can also help you!