1. Pressure testing machine
Whether it is from the perspective of cost or the difficulty of maintenance, the number of stress testing machines should be appropriate. For example, after deploying Jmeter on a server of 8C16G, according to my personal test comparison data, it is best to configure the number of threads ≤ 1500. Too much performance loss and high delay; too little and waste. Controller and agent: The number of simulated concurrent threads exceeds 5K. It is recommended to reserve a dedicated controller machine, mainly to avoid the impact of agent machine data reporting. Service authorization: If the pressure test startup and service configuration are both root privileges, then in the Linux environment, you need to authorize jmeter and jmeter-server, the command is
chmod 777 jmeter
2. Service communication
All the stress testers and the service under test should preferably be in the same network segment to reduce the delay problem as much as possible. If the stress test machine is on the internal network, and the access request address (now it is a unified gateway domain name) is on the external network, you should pay attention to one point: there is generally a bandwidth limit from the internal network to the public network. It is best to communicate with Operation and maintenance confirmation. 3. The service startup pressure test machine is in place, the service authorization configuration is completed, the script is written, and the network is ok, so how to start it in NGUI mode (that is, the linux environment)? Many other blogs on the Internet write about using the command ./jmeter-server to start the pressure measurement service, but this has a disadvantage, as long as the service connection is interrupted, the pressure measurement service will be unavailable. However, if you start the jemter-server of the agent machine as a background service, you don’t have to worry about the service being unavailable. The command is:
nohup sh jmeter-server &
There are two ways to start the pressure test to specify the start of the pressure test machine:
./jmeter -n -t /path/test.jmx -R 127.0.0.1,127.0.0.2Start all stress machines:
./jmeter -n -t /path/test.jmx -r
The following are supporting learning materials. For friends who do [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse also accompanied me through the most difficult journey. I hope it can help you too!
Software testing interview applet
The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!
The following interview question sections are covered:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics
Information acquisition method:
