Jmeter pressure test environment preparation

Jmeter performance monitoring

1. Configure the jmeter environment on the test machine: Download two things from the http://jmeter-plugins.org/downloads/all/ Website:JMeterPlugins-Standard-1.1.3.zip,ServerAgent-2.2.1.zip
2. After the standard ZIP package is decompressed, The jmeterplugins-standard. jar files are placed under XXX \ apache \ jmeter \ Lib \ Ext. After jmeter is restarted, you can see that a lot of content is added to the listener by right-clicking the thread group, add [email protected]-perfmon metrics collector to the existing project as the monitoring server data.
3. After adding [email protected]-perfmon metrics collector, add row to add information about the data to be monitored, such as CPU, memory, disks/Io, and TCP, the default port is 4444.
4. Configure the server, decompress the serveragent.zip package, and put it on the server:

• Linux: run the CD command to this folder and enter the command./xxxxxx/startagent. Sh. Note: If the client is not configured with port 4444, you need to start the port set by the client. The command is. /startagent. sh -- UDP-port 0 -- TCP-port XXXX, of course, XXXX is the set port number.
• Windows: Double-click startagent. bat. The default port 4444 is enabled.

5. Click start on the testing machine to start the Interface Test and stress test. In the selected [email protected]-perfmon metrics collector, you can view the performance information from the server.

Jmeter distributed deployment

The procedure for using multiple machines to generate loads is as follows:

1. Install jmeter on all machines that want to run jmeter as the load generator, and determine one of them as the controller and the other as the agent.
2. In the jmeter % jmeter_home %/bin directory of the controller machine, locate the jmeter. properties file and edit the file:

Search: remote_hosts = 127.0.0.1, modify to: remote_hosts = 10.8.39.114: 1099, 10.8.33.181: 1099, localhost: 1099

Pay special attention to the port. Some information indicates that port 1644 is the default RMI port number for communication between the Controller and agent of jmeter. However, during the test, it is found that the port is set to 1644 and failed to run, change to 1099 and then run it. In addition, pay attention to whether the firewall is enabled for the agent host.

3. Run the jmeter-Server File on all agent machines.

4. start the jmeter application jmeter on the controller. bat, select the menu "run" ---> "remote start" ("Run" ---> "remote start") to start the agent separately, you can also directly select "remote start all" ("remote start all") to start all agents. When

During remote access, a line is displayed on the console: starting the test on host [IP]: 1099 @...., when the remote execution ends, a row: finished the test on host [IP]: 1099 @... will be printed @....

Notes:

1) In the jmeter distributed control process, the number of threads started by each agent is equal to the configuration in the thread group, not evenly allocated to the configuration in the thread group, the number of threads tested by each agent is the number of threads you configured on the controller. That is to say, the number of threads on the controller is 100.

Execute and loop once, so my deployment will have a colleague trigger the number of 300 (100x3) threads, execute immediately, and execute once. Instead of sharing 100 threads with three machines.

2) When you want to run the agent on the contreller machine, run the jmeter-Server File before jmeter. bat.

3) Make sure that the machine's firewall is disabled during configuration.

References:

Performance monitoring plug-in:
Http://www.tuicool.com/articles/RbAN3ea
Performance monitoring introduction:
Http://blog.csdn.net/defonds/article/details/41650813

Jmeter pressure test environment preparation