1 Purpose: Check the carrying capacity login interface
2, the pressure measuring machine environment
3, press configuration: 2C4G, a virtual machine
4, script preparation: 1000 thread
5, an interface: interface is very simple, three parameters do not need parameterization;
6, the script finished, ran once, normally available;
7, generates a file .jmx, thrown directly above the press;
8, following the start bin directory jmeter,. / Jmeter.sh xxx.jmx -l yyy.jtl thus launched a direct pressure measurement starts jmeter
Specific command is as follows:
[root@stress bin]# ./jmeter.sh -n -t /opt/apache-jmeter-5.1.1/scripts/login1000.jmx -l login1000.jtl
9, pressure measurement time of 40 minutes, stopped manually jmeter, control + c;
10, yyy.jtl find the generated files under bin directory, you need to turn it into html files for easy viewing (in fact, can generate jtl time while generating html files, but I have not the operation was successful, so divided in two steps)
Command is as follows:
[Root @ stress bin] # ./jmeter -g login1000.jtl -o / tmp / ResultReport1000 (this directory must not exist)
Then wait for execution is completed, you can see it directly pressed test results
It is not super easy ah! ! !
Finally, talk about, in fact, still very good preliminary preparation da, press preparation, installation jmeter, because the next is Linux, no gui interface, can only see the command;
Resource consumption of the supplement under pressure measured during the top command, is pushed under the supervision of the machine, my 1000 thread, and it's directly cpu burst. . .
I have a question, cpu utilization why more than 100%? ? ?
Continue to study. . .