NoMachine Support

Your questions answered

Knowledge Base

Searching in: Articles & FAQs
Filter the search results
Applies to:
Last update:
Searching in: Articles & FAQs
ID: AR02N00875
Applies to: NoMachine Software
Added on: 2016-02-10
Last update: 2021-01-13
Reading NoMachine statistics

To retrieve statistics for your NoMachine session, run the menu panel within the session by Ctrl+Alt+0 or click on the page peel. Click on Connection, then click on 'Take the statistics' and save them on your local device.

Statistics are made of four sections:

1) NX Cache Statistics

2) NX Client Side Protocol Statistics

3) NX Server Side Protocol Statistics

and a summary of data traffic:

4) NX Protocol Summary

 

1) NX Cache Statistics

This section displays the amount of data cached for each request. A request is identified by a code (e.g. #12, #243) which allows developers to identify the type of request.

A request is a data set traveling from server to client. Only some requests expects a reply. A reply is a data set traveling from client to server.

When the request is cached (because it was already handled before) it means that data for the request are not sent because they are already available in cache: only a few bits are sent to the other proxy to tell where to retrieve the cached data. High cache values indicate an optimized use of the bandwidth.

For example, this summary of cache operations:

cache: 16777216 bytes (16384 KB) available at server.
             16777216 bytes (16384 KB) available at client.

             171660 bytes (167 KB) allocated at server.
             415180 bytes (405 KB) allocated at client.

indicates that only 167 KB of cache are effectively used on the server, while the server is able to cache up to 16384 KB.

Cache allocated on server and client increases till the maximum value during the life of the session. Default is indicated in the 'Cache limit' field, for example: 3000/819 KB. It means that are allowed up to 3000 requests in cache for a maximum size of 819 KB. 
 

2) NX Client Side Protocol Statistics

This section refers to data traffic sent from the server to the client and displays:

Bits In - bit size of the request generated by an application (before the NX compression)

Bits out - bit size after the NX compression

Bits/Reply - the average bit size on per-request basis

Ratio - the compression ratio

for each reply (sent for a request)  and event (originated on the client, e.g. mouse and keyboard inputs). 

Summary of this section reports how long the proxy has been idle an running, for example:

time: 5080 ms idle, 193 ms running.

and other information such as:

link: 97 frames in, 77 frames out, 64 writes out.

        125 bytes (0 KB) used for framing and multiplexing.

            4 audio messages, 48 bytes (0 KB) in, 56 bytes (0 KB) out.

           3 slave messages, 311 bytes (0 KB) in, 317 bytes (0 KB) out.

          Protocol compression ratio is 1.818:1.

          3491 B/s average, 514 B/s 5s, 0 B/s 30s, 16568 B/s maximum.

This last line in particular indicates the average value of bits transferred on the network from client to server overall (3491 B/s average), in the last 5 seconds (514 B/s 5s), in the last 30 seconds (0 B/s 30s) and the maximum peak (16568 B/s maximum). It displays the bandwidth that the client is using.

In case of connection by NX protocol with UDP enabled, there is an additional line showing the UDP packages transferred (RT), for example:

10 RT messages in, 1913 RT messages out, 0 lost, 0 corrected.  

 0 drops, 0 bytes (0 KB) in, 2327676 bytes (2273 KB) out.


 where:

'RT messages in' refers to number of received UDP messages

'RT messages out' refers to number of sent UDP messages

'Corrected' refers to the number of corrected UDP messages by Forward Error Connection (FEC)

'Drops' refers to number of dropped UDP messages

'bytes in' refers to the number of bytes received

'bytes out' refers to the number of bytes sent
 

3) NX Server Side Protocol Statistics

This section refers to data traffic sent from the server to the client and displays three kind of  tables:

- Request

- Pack

- Render

Table for request is the general table, the other ones are specific for compressed images (Pack table) and requests related to the Render extension (Render table). Requests #243 listed in the Pack table and grouped by encoding type such as Jpeg, Vp8, etc... These are the code numbers for the various encoding types:

#35 jpeg
#93 VP8
#97 H264

For example:

Pack     Total  Bits In  Bits Out    Ratio
-------------------------------------------------------------------------------------
#35   64  132722688 (16201 KB) 1380032 (168 KB)   96.174:1

means: 64 Jpeg images, 16 MB compressed to 168 KB with compression ratio 96:1

 

Requests #252, related to the X Render extension, are instead listed in the Render  table.

 

All of these tables reports, as for the client side statistics:

Bits In - bit size of the request generated by the X client (before the NX compression)

Bits out - bit size after the NX compression

Bits/Reply - the average bit size on per-request basis

Ratio - the compression ratio

and a general summary. 

In the general summary it's indicated the bandwidth used by the server, for example:

3452 B/s average, 961 B/s 5s, 4215 B/s 30s, 19509 B/s maximum.

and also latency measured on the network in the last 5 and 30 seconds . For example:

22 ms latency 5s, 22 ms latency 30s.

 

4) NX Protocol Summary

This section reports the final and global data on the overall performances. For example:

overall: 33628782 bytes (32840 KB) in, 42195 bytes (41 KB) out.

means that 41 KB have been sent on the network against the original 32 MB generated by applications.