|
Measures reported by KeepAliveTest
The HTTP protocols support the ability to send multiple requests across a single HTTP session. So a web server can receive hundreds of new HTTP requests per second. If every request was allowed to keep the connection open indefinitely, the server could become overloaded with connections. On Unix / Linux systems, this could lead to a file table overflow very easily.
This test reports statistics pertaining to the HTTP_level keep alive system (Persistent connections) in the web server.
The measures made by this test are as
follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Keep_alive_count |
The number of sessions waiting for a keepalive connection |
Number |
|
| Keep_alive_max_count |
The maximum number of sessions that the server allows to wait at one time |
Number |
|
| Keep_alive_hits |
The number of times a request was successfully received from a connection that had been kept alive |
Number |
|
| Keep_alive_flushes |
The number of times the server had to close a connection because the Keep_alive_count exceeded the Keep_alive_max_count |
Number |
|
| Keep_alive_timeout_count |
The number of times the server terminated keep-alive connections as the client connections timed out, without any activity |
Number |
|
| Keep_alive_timeout_rate |
The number of seconds the server will allow a client connection to remain open with no activity |
Secs |
|
|