Performance statistics
Performance Statistics🔗
Tempesta FW has a set of performance statistics counters that show various aspects of Tempesta FW operation. The counters and their values are self-explanatory. Performance statistics can be shown when Tempesta FW is loaded and running.
Below is an example of the command to show the statistics, and the output:
$ cat /proc/tempesta/perfstat
Minimal response time : 0ms
Average response time : 0ms
Median response time : 0ms
Maximum response time : 0ms
Percentiles
50%: 0ms
75%: 0ms
90%: 0ms
95%: 0ms
99%: 0ms
SS work queue full : 0
SS work queues sizes : 0 0 0 0 0 0 0 0
SS backlog's sizes : 0 0 0 0 0 0 0 0
Cache hits : 0
Cache misses : 0
Cache objects : 0
Cache bytes : 0
Client messages received : 2918206
Client messages forwarded : 2918206
Client messages served from cache : 0
Client messages parsing errors : 0
Client messages filtered out : 0
Client messages other errors : 0
Clients online : 0
Client connection attempts : 2048
Client established connections : 2048
Client connections active : 0
Client RX bytes : 309329836
Client max streams number exceeded : 0
Client priority frames number exceeded : 0
Client rst frames number exceeded : 0
Client settings frames number exceeded : 0
Client ping frames number exceeded : 0
Client window update frames number exceeded : 0
Server messages received : 2918206
Server messages forwarded : 2918206
Server messages parsing errors : 0
Server messages filtered out : 0
Server messages other errors : 0
Server connection attempts : 8896
Server established connections : 8896
Server connections active : 32
Server connections schedulable : 32
Server RX bytes : 11494813434
Server successful TLS handshakes : 1012
Server failed TLS handshakes : 12
Tempesta health statistics:
HTTP '404' code : 2
HTTP '5' code : 3
Cache objects – the current number of objects stored in the cache,
the number of cached objects, will be decreased on the removal.
Cache bytes – number of bytes at the moment stored in the cache.
Note that no-cache requests aren’t represented neither in Cache hits nor in
Cache misses since Tempesta FW doesn’t check the cache for such requests.
Cache hits and Client messages served from cache may vary significantly.
Cache hits counts prepared stale responses for cache-control: stale-if-error
and cache_use_stale directive. These stale responses might not be sent to the
client, for example, when a response is successfully received from the upstream
server. Therefore, such responses are not counted in Client messages served from cache.