A brief description of the Apache AB test mainly has those key indicators

First, the principle of AB

AB is the abbreviation for the Apachebench command.

Ab ab url address to access. Its test target is based on the url So it can be used to test apache load pressure, can also test nginx lighthttp , tomcat , iis web

The AB command is very low on the computer that emits the load, and it does not occupy a high CPUor consume a lot of memory. But it will cause a huge load on the target server, which works like a CC attack. You also need to be aware of your own testing, or too much load at a time. May cause the target server resources to run out, serious even causes the panic.

Server software:apache/2.0.54

platform Apache version 2.0.54

Server hostname:127.0.0.1

Server Host name

Server port:80

Server Port

Document Path:/index.html.zh-cn.gb2312

test the page document

Document length:1018 bytes

Document Size

Concurrency level:1000

Concurrency number

Time taken for tests:8.188731 seconds

Duration of the entire test

Complete requests:1000

number of requests completed

Failed requests:0

number of failed requests

Write errors:0

Total transferred:1361581 bytes

network traffic in the entire scene

HTML transferred:1055666 bytes

The amount of HTML content transferred throughout the scene

Requests per second:122.12 [#/sec] (mean)

one of the most concerned indicators, equivalent to the number of transactions per second in LR, followed by mean in parentheses indicates that this is an average

Time per request:8188.731 [MS] (mean)

two of the most concerned indicators, equivalent to the average transaction response time in LR, followed by mean in parentheses indicates that this is an average

Time per request:8.189 [MS] (mean, across all concurrent requests)

average of actual run time per request

Transfer rate:162.30 [Kbytes/sec] Received

average traffic on the network per second can help eliminate the problem of extended response times due to excessive network traffic

Connection Times (MS)

Min MEAN[+/-SD] Median max

Connect:4 646 1078.7 89 3291

processing:165 992 493.1 938 4712

waiting:118 934 480.6 882 4554

total:813 1638 1338.9 1093 7785

The decomposition of time consumed on the network, the specific algorithm of each data is not very clear

Percentage of the requests served within a certain time (MS)

50% 1093

66% 1247

75% 1373

80% 1493

90% 4061

95% 4398

98% 5608

99% 7368

100% 7785 (Longest request)

the response of all requests in the entire scene. Each request in the scene has a response time, where theuser response time is less than 1093 milliseconds, andThe user response time is less than 1247 milliseconds, the maximum response time is less than 7785 milliseconds

Because for concurrent requests, theCPU is not actually processed at the same time, but is rotated on a per-request basis, so basically the first time per Requests is approximately equal to the second times per request time multiplied by number of concurrent requests

A brief description of the Apache AB test mainly has those key indicators