Http_load Use

-parallel abbreviation -p: meaning is the number of concurrent user processes -fetches abbreviation -f: meaning is the total number of visits -rate abbreviation -r: meaning is the frequency of access per second -seconds abbreviation -s: meaning is the total access time http_load -p number of concurrent access processes -f total number of access URL files that need to be accessed http_load -r access frequency per second -s access time URL file to be accessed

コマンドhttp_load-p 10 -f 100url.txtを実行します

1.49 fetches, 2 max parallel, 289884 bytes, in 10.0148 seconds Explain that 49 requests were run in the above test, the maximum number of concurrent processes is 2, the total transmitted data is 289884bytes, and the running time is 10.0148 seconds 2.5916 mean bytes/connection Explain the average amount of data transmitted per connection 289884/49=5916 3.4.89274 fetches/sec, 28945.5 bytes/sec Explain that the response request per second is 4.889274, and the data transmitted per second is 28945.5 bytes/sec 4.msecs/connect: 28.8932 mean, 44.243 max, 24.488 min Explain that the average response time per connection is 28.8932 msecs, the maximum response time is 44.243 msecs, and the minimum response time is 24.488 msecs. 5.msecs/first-response: 63.5362 mean, 81.624 max, 57.803 min 6、HTTP response codes: code 200 -- 49 Explain the type of open response page. If there are too many types of 403, you may need to pay attention to whether the system has encountered a bottleneck. Special note: Here, the indicators we generally pay attention to are fetches/sec, msecs/connect Their corresponding common performance index parameters Qpt-the number of response users per second and response time, the response time per connection user. The result of the test mainly depends on these two values. Of course, only these two indicators can not complete the performance analysis. We also need to analyze the server's cpu and men to draw conclusions.