The explanations are as follows:
-
-
Server Software
-
The name of the
-
server software software.
-
-
Server Hostname
-
-
the host name of the server being tested.
-
-
Server Port
-
-
The listening port of the Web server being tested.
-
-
SSL/TLS Protocol
-
It
-
will only print if it is used. Represents the parameters for client and server negotiation.
-
-
Document Path
-
The
-
request URL.
-
-
Document Length
-
The
-
first successful return of the document size, if the length of the document changes at the time of testing, this response will be treated as an error, so if the failed request has a length type of error, you can consider whether it is because the URL being measured is dynamically generated due to inconsistent return length.
-
-
Concurrency level
-
-
number of concurrent users during the test (concurrency)
-
-
Time taken for tests
-
-
the time to complete the test, starting from the first time the socket connection was created, until the last response is received.
-
-
Complete requests
-
-
the number of successful responses received.
-
-
Failed Requests
-
-
the number of failed requests. If this is greater than 0, an additional line will be printed after that, indicating a detailed breakdown of the specific failure, listing the connection failure, the failed read response, the incorrect length, or the number of requests for the exception. Read response failure may be that the server is too late to process these requests, the supported concurrent connections are too few to shut down, and therefore no return, resulting in a read response failure. Incorrect lengths are likely to be normal and require further analysis. The connection failure may be that the server being tested did not start. The exception may be some of the exceptions that appear in the returned results page. The number of non-2XX response codes is not counted, i.e. non-2XX codes are not counted as failed requests.
-
-
Write errors
-
-
Write request error, generally should not appear, this is an AB error (broken pipe).
-
-
NON-2XX Responses
-
-
Non-2XX Code response results, if all responses are 2XX, no output
-
-
Keep-alive Requests
-
-
number of connections that keep active requests
-
-
Total Body Sent
-
-
If the test process is configured to send packets, this represents the total number of bytes sent during the test process. If no packets are sent, this line is not displayed.
-
-
Total transferred
-
-
represents the sum of the response data length for all requests, including the header information for each HTTP response data and the length of the body data. Note that this does not include the length of the HTTP request data, only the total length of the application layer data that the Web server flows to the user's PC.
-
-
HTML Transferred
-
-
represents the sum of the body data in the response data for all requests, minus the length of the header information in the HTTP response data in total transferred.
-
-
Requests per second
-
-
the number of requests processed per second, that is, Qps,rps,tps. This value is calculated by: Number of requests completed/total time consumed, resulting
-
-
Time per request
-
-
the time spent on each request. The first time to wait for a user: Total time/Total request/concurrency, this formula indicates that the concurrency level specified by the stress test has an impact on performance, the smaller the concurrency, the smaller the user request waiting time, the better the performance, the faster the user experience, the better.
-
The
-
second is the reciprocal of the server request wait time for throughput, or it can count: User request wait time/concurrency
level
-
-
Transfer Rate
-
-
transfer speed, the formula
totalread / 1024 / timetaken is
Percentage of the requests served within a certain time (MS)
Represents the total number of requests less than a certain time during the whole process
Connection Times (ms)-from http://my.oschina.net/lubia/blog/177186
Min MEAN[+/-SD] Median max
Connect:socket Link Establishment consumption, representing the network condition good or bad
Processing: Write buffer consumption + link consumption + service-side consumption
Waiting: Write buffer consumption + link consumption + service-side consumption + read data consumption
Total: Overall time for a single transaction
"Original" AB result parameters Detailed
