Dealey of getting update of the light streamer update

Yousef2006

Hi Every one

Currently I'm using Subscription with type mode="MERGE",

with Below information
subscription.setDataAdapter("DEFAULT")
subscription.setRequestedSnapshot("yes")
subscription.setRequestedMaxFrequency("1")

But the feeding ( there id Dealey by 200 millisecond around the first message and Subscription 1:1 update: message )

Is there any way to change the configuration to get the data speed

2024-11-10 09:08:05.608571|DEBUG|lightstreamer.stream|

2024-11-10 09:08:05.609346|DEBUG|lightstreamer.protocol|

2024-11-10 09:08:05.639346|DEBUG|lightstreamer.subscriptions|Thread-2 (_hx_local_0)|Subscription 1:1 update:

Yousef2006

this is the feeding message

2024-11-10 09:08:05.608571|DEBUG|lightstreamer.stream|LS_IO|HTTP event: text(U,1,1,1211|1211|53.9|0|0|0|2024-11-07 15:19:52|0|0|0|0|0|0|0|0|0|-|U|2024/11/10 04:40:40.000|2024-11-10 07:40:40.000|53.9|0|0|0|0|48.55|59.2|#|#|#|#|#|#|#|#|2024-11-10 07:40:40.000|#|#|#|#|#|#|#|#|#|#|#|#|#)

2024-11-10 09:08:05.609346|DEBUG|lightstreamer.protocol|Thread-2 (_hx_local_0)|U,1,1,1211|1211|53.9|0|0|0|2024-11-07 15:19:52|0|0|0|0|0|0|0|0|0|-|U|2024/11/10 04:40:40.000|2024-11-10 07:40:40.000|53.9|0|0|0|0|48.55|59.2|#|#|#|#|#|#|#|#|2024-11-10 07:40:40.000|#|#|#|#|#|#|#|#|#|#|#|#|#

2024-11-10 09:08:05.639346|DEBUG|lightstreamer.subscriptions|Thread-2 (_hx_local_0)|Subscription 1:1 update: [1:StringVal(1211),2:StringVal(1211),3:StringVal(53.9),4:StringVal(0),5:StringVal(0),6:StringVal(0),7:StringVal(2024-11-07

Giuseppe Corti

Hi @Yousef2006 ,

Please could you check the Lightstreamer server configuration? In particular the parameter <max_delay_millis> into the lightstreamer_conf.xml file. Indeed, it is that parameter that can introduce a delay before the data is sent.

_<!-- Optional. Longest delay that the Server is allowed to apply to
     outgoing updates in order to collect more updates in the same
     packet. This value sets a trade-off between Server scalability
     and maximum data latency. It also sets an upper bound to the
     maximum update frequency for items not subscribed with unlimited
     or unfiltered frequency.
     Default: 0. -->
<max_delay_millis>30</max_delay_millis>_

Yousef2006

it's Zero

Yousef2006

subscription.setRequestedSnapshot("yes")
subscription.setRequestedMaxFrequency("1")

If i change the value of the MaxFrequency to 100 did you think the update will be more faster

and what about the RequestedSnapshot value ??

Alessandro.Carioni

By default, the client does not impose any frequency limits on subscriptions. Therefore, if you want to receive updates at the maximum speed the server can provide, you can skip setting this parameter. The setRequestedMaxFrequency method is primarily useful if you need to reduce the update frequency.

The setRequestedSnapshot method determines whether the client should wait for the first fresh update or if the last update produced by the server (which may be stale) is acceptable.

Therefore, if you want to receive updates as quickly as possible, you should omit the call to setRequestedMaxFrequency and set setRequestedSnapshot to yes.

By the way, the attached log shows that the delay between the first message and the third message is only 30 milliseconds, not 200 ms.

Yousef2006

Alessandro.Carioni

what about this
subscription.setRequestedBufferSize("1")

Alessandro.Carioni

Before taking any actions, it is crucial to understand your objectives.

For example, do you have any evidence that the client's update consumption rate is significantly slower than the server's update production rate?
If not, there is no need to adjust the default configuration parameters.