Poor performance with WebSocket Streaming when having bad latency

[lidanh]

OK,

Thank you Giuseppe!

[HoangTranVinh]

Dear all,
I have the same problem.
I am lucky when I found this thread

I want to know:

If I set the MSS:
<MSS>10000</MSS>

then the value of <sendbuf> should be ?
and other relate parameters (if any)

Thanks for your support,
HoangTV.

[giuseppe.corti]

Hi HoangTV,

If you decide to change the factory default values for the parameters like <sendbuf> and <MSS> then their tuning should be the result of intense tests in your typical scenario.

In any case, I expect that the value of <sendbuf> is always kept higher than that of <MSS> (even slightly, in your case i can speculate 12000).
But, please let me to repeat that you should thoroughly test the choices taken.

Regards,
Giuseppe

[HoangTranVinh]

Many thanks
Regards,
HoangTV

[Alessandro]

In most cases, acting on <sendbuf> only should be enough, without touching <MSS>. Try to increase sendbuf as much as you want (up to 2147483647) and see if the situation improves.

Here is how it works.

By default, Lightstreamer keeps a tiny sendbuffer (1600 bytes). This allows the server to implement very fast detection of network congestion and adaptively throttle the data flow. What happens with a small sendbuffer is that the congestion windows is kept small as well. This works great with normal streaming activity. But if a huge amount of data needs to be delivered in a short time (similar to a normal download activity), then such a small sendbuffer would slow down the data transfer a lot. That's why increasing the sendbuffer, possibly to very large values (for example, try 100,000,000 bytes), will boost download performance.