JMeter Distributed Testing Stepbystep（JMeter分布式测试Stepbystep）.pdfVIP

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 doesnt use 192 or 10 ip address, there shouldnt 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 youve made sure the systems are ready, its 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, its 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 doesnt 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. 1. Open jmeter-server.bat in a text editor 2. go to line 44 and find “:setCP” 3. edit “START rmiregistry” to