Shulou(Shulou.com)06/02 Report--

Install ab

Yum-y install httpd-tools

-c 100 indicates that the number of concurrent users is 100

-n 100 means the total number of requests is 100

Ab-c 100-n 100 http://127.0.0.1/index.php

Server Software: nginx/1.10.2 # platform nginx version 1.10.2

Server Hostname: 127.0.0.1 # server hostname

Server Port: 80 # server port

Document Path: / index.php # tested page documentation

Document Length: 307 bytes # document size

Concurrency Level: 100 # concurrency

Time taken for tests: 9.764 seconds # duration of the entire test

Complete requests: number of requests completed by 100 #

Failed requests: number of failed requests for 0 #

Write errors: 0

Non-2xx responses: 100

Total transferred: 51300 bytes # Network traffic in the entire scenario

HTML transferred: 30700 bytes # the amount of HTML content transferred throughout the scene

Requests per second: 10.24 [# / sec] (mean) # throughput, the number of requests processed per unit time under 100 concurrent users. Mean represents the average of 10.24 times per second. The greater the value, the better.

Time per request: 9764.459 [ms] (mean) # APCge request waiting time for users, and mean represents the aPCge

Time per request: 90.303 [ms] (mean, across all concurrent requests) # average of actual elapsed time per request

Transfer rate: 5.55 [Kbytes/sec] received # average network traffic per second, which can eliminate the problem of excessive network traffic leading to longer response time.

Connection Times (ms)

Min mean [+ /-sd] median max

Connect: 0 4 1.3 4 6

Processing: 11 1784 2708.6 95 9018

Waiting: 5 1784 2708.7 95 9018

Total: 11 1788 2709.3 99 9022

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

50% 99 # 50% of users respond less than 99 milliseconds

66% 1269 # 66% of users' response time is less than 1269 Ms

75% 3275 # 75% of users respond less than 3275 milliseconds

80% 4275

90% 6762

95% 8012

98% 8763

99% 9022

9022 (longest request) # maximum response time less than 7785 milliseconds

# concurrent request cpu is not processed at the same time, but rotates one by one according to the time slice obtained by each request, so basically the first Time per request time is approximately equal to the second Time per request time multiplied by the number of concurrent requests.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.