Hi Ahmed,

The monitor states that at the moment the screenshot was taken:
  • the server allocate about 290 MBytes of total memory for the heap (of which about 5 are free).
  • 14 sessions are established 12 in streaming mode, 2 in polling mode. Furthermore, since 14 connections are active this means 1 session : 1 connection.
  • 365 Items are subscribed and the server in the last 2 second received an average of 39.46 upd/s from the adapters.
  • The server sends to the client an average of 114.39 upd/s and from the start 578 updates have been lost (the server had to discard them from the event buffer of a client).
  • No client messages activity.
  • The thread activity is quite calm, no queued tasks.


The server situation generally looks good and the only possible warnings seems to be:
  1. the low amount of free heap, please could you confirm the settings for JVM memory option in the LS.bat launch script?
  2. the messages lost, this may mean that one or more clients fail to processing all messages received from the server or the network bandwidth is not adequate to flow of data incoming.


Please note that more detailed info, from the same source of the monitor console, can be find in the LightstreamerMonitorText logger. A 'grep' of all lines of that logger can give a more complete picture of the performance of the server during the day.

You can find the complete description of the fields shown in the Monitor Console in the final paragraph (4.2.1) of the "General Concepts.pdf" document.
For a map of the fields used in the console HTML page, please refere to the source code, /src/index.html, of this GitHub project.

Regards,
Giuseppe