Jmeter is a java application for CPU and memory consumption is relatively large, and therefore, when the need to simulate thousands of concurrent users, using a single machine to simulate all of concurrent users bloated, and even lead to memory overflow error JAVA. To make jmeter tool provides greater load capacity, jmeter a dapper With the use of multiple machines at the same time the mechanism of load.
So, how to achieve more than one machine while the load is running it? Of course, not more than one person sitting in front of multiple load machine, start a call, it started simultaneously jmeter. In this way stupid, it is difficult to achieve true synchronization. In fact, we jmeter by a single client can control multiple remote jmeter servers that are synchronized with the server stress test.
Jmeter by remote operation, the tester can span multiple low-end computers copy test, so you can simulate a relatively large pressure on the server, a client jmeter instance, in theory, can control any number of remote jmeter example, through them and collect test data. As such, there is the following features:
* Save test sample data to the local machine
* Execution engine through a single machine to manage multiple jmeter.
* There is no need to copy the program to test each machine, jmeter GUI client it will be sent to each jmeter server.
* Each jmeter remote server perform the same test plan, jmeter not do load balancing during execution, each server will run a complete test plan.
In a 1.4G Hz ~ 3GHz CPU, 1GB memory JMeter client, processing thread 100 to 300. But the Web Service exception. XML processing is CPU-intensive operations, it will quickly consume all of the CPU. In general, as the core technology in XML applications, its performance would be 10% to 25% of the ordinary Web applications. Further, if all of the load is generated by a machine, the NIC and switch ports may create a bottleneck, so a number of threads JMeter client should not exceed 100.
Using JMeter remote mode and does not consume more resources than running a non-independent GUI test the same number. However, if you use a lot of JMeter remote server, the client may cause overload, or a network connection is congested.
Generating a load using multiple machines following steps:
(1) mounted on the machine all desired operating jmeter jmeter generator as a load, and determining one of the machines as a controller, as other machines agent. Jmeter-server files then run on all machines agent (assuming the two machines 192.168.0.100 and 192.168.0.101 as agent)
(2) in the bin directory jmeter the controller of the machine, find jmeter.properties file, edit the file:
Find: remote_hosts = 106.52.156.148: 1099 modified to: remote_hosts = 192.168.0.100: 1099,192.168.0.101: 1099
(3) Start jmeter applications on the machine controller, select the menu "Run" ---> "Remote Start" to start the agent, respectively, can also directly select "Remote Start All" to all of the agent started.
