Push and Subscription Buffering

[Cerogil]

Sorry for the late response to this. We had a workaround by limiting the amount of data we were pushing at one time to less than a thousand.

We are not using MERGE mode, we are using COMMAND mode.

When Lightstreamer goes to push the thousands of data to the client, the Lightstreamer command window shows the following: "... < INFO> Lost x updates on unfiltered/RAW subscription for item ..." The x ranges anywhere from 1 to thousands. Many of these lines show up, and they appear to add up to the number of items that do not make it to the client.

We want to stay in command mode to have a snapshot available for other users to grab from and to handle the many updates throughout the day. We'd rather not limit the pushes, and do not a way to limit the pushes from a snapshot for new clients using the same subscription - they lose the data.

Any ideas why this might be occuring?


Thanks.

[DarioCrivelli]

In COMMAND mode, the "one event per second" limitation imposed by Lightstreamer Moderato only affects single keys, hence the snapshot, which is made up of different keys, should flow fast.
However, your snapshot seems to be very large, so the <max_buffer_size> limitation applies in this case.
This setting avoids that the event queue for a single subscription grows beyond any limit.

If you know that snapshots of many thousand events can be expected, then you should increase <max_buffer_size> accordingly.
Note that this may affect all event queues, related to items in RAW mode or with the "unfiltered" flag, for which the Data Adapter event rate fairly exceeds the "one event per second" outbound limitation.
In the forthcoming 3.6 release of the Server, things are going to change and <max_buffer_size> will no longer limit event queues when they are related with COMMAND mode snapshot.