Recently, when using JMeter for load testing, I found that taking the concurrency of more than 500 processes simulated by a single machine as an example, some of them were unable to do so or could not truly reflect the actual situation. During execution, JMeter itself will automatically shut down. To solve this problem, distributed testing can be used. Running multiple machines to run the so-called proxy to share the pressure of JMeter itself (this is the same as LODARUNNER) and to obtain a larger number of concurrent users requires some modifications to the relevant configuration parameters and file permissions, as follows:

1. Install JMeter on all machines that are expected to run JMeter as a load generator, and make sure that one machine is a controller and the other machines are agents-suppose we use two machines, 192. 168.0.1and192./kloc.

2. Find the bin directory under the JMeter installation directory of the controller machine, then find the file JMeter.properties and open it with notepad or other text editing tools;

3. Find the string "remote_hosts=" in the open file, and you can find the line "remote _ hosts =127.0.0.1". Where 127.0...0. 1 stands for the machine running the JMeter agent and needs to be modified to "remote _ hosts =192.168.0.1:1099, 192.168.0.2: 1099 "-where1099 is the default RMI port number for communication between JMs (personal note: just change this file on the machine you want to be a controller; Files on the proxy computer can be ignored)

4. Save the file, and then start the jmeter-server file on the machine as the controller and the jmeter-server file on the machine as the agent in turn (personal note: if it is the jmeter of WINDOWS system version, it is the batch file to start jmeter-server.bat, and the LINUX system is a jmeter-server file without suffix, but it needs to be modified to be executable, which will be mentioned in detail later), and restart JMeter.bat on the controller machine. Remote start menu item, here you can see that there are two IP addresses,192.168.0.1,192.168.0.

If you want the computer to execute it, you can click to change the IP address of the computer. If you want to do both, you can click the "Remote Run All" menu under the Run menu.

6. Sometimes there are too few machines as agents to meet the demand. If you need to treat the computer as a controller as an agent, you need to modify the JMeter.properties file and write it into the IP address of the controller. At the same time, at this time, you need to open jmeter-server.bat in the bin directory under JMeter in the controller computer first, then open JMeter.bat and enter run->; Remote start menu, you can see that the controller is also running as a remote machine. (For the sixth point, I personally need to make a detailed confirmation after the field test: if it is under LINUX, the permissions of this file will still be modified, jmeter-server will call a script file named jmeter, and the permissions of its jmeter file will also be modified to be executable, and it is very important that the jmeter-server file of each called agent machine can only be called when it is executed. )。

/* styledefinitions */table. msonormaltable {MSO type-name: ordinary table; MSO-t style-rowband-size:0； MSO-t style-colband-size:0； Mso-style-noshow: yes; MSO-style- priority: 99; Mso-style-qformat: yes; MSO-style-parent:“”； MSO-padding-alt:0 7px 0 7px； MSO-para-margin:0； MSO- Alignment-Margin-Bottom: 0; MSO- Paging: Widow-Orphan; font-size: 14px； MSO-bidi-font-size: 15px； Font series: "Calibri", "sans-serif"; MSO-ascii-font-family:Calibri； MSO-ascii-theme-font:minor-Latin； MSO- Hans-font -font-family:Calibri；; MSO- Hans-Theme-Font: Minor-Latin; MSO-font-kerning: 1px； }