Yes I can confirm that with your javascript library modification I could scale up to 30 messages\second with Polling instead of 20! and I did not test for more because I don't need more than 30 :)
...
Type: Posts; User: ReVaN01
Yes I can confirm that with your javascript library modification I could scale up to 30 messages\second with Polling instead of 20! and I did not test for more because I don't need more than 30 :)
...
I performed some new tests and I totally eliminated DOM modifications (HTML 5 canvas use) which I realized they were slowing the whole polling process down. Surprisingly I got an almost constant 20...
Ok so here are some tests I carried out with better proof of what is going on. Excuse me for my previous post, as I am still experimenting with settings etc..
These are my server settings for the...
Right now I am able to push for example 800 msgs/s to a client using WS-STREAMING which is Ok.
What I want to test now is, if the client does not support WebSocket and hence falls back to...
Thanks for your tips, the "<max_delay_millis>" did in fact work and also I set <max_buffer_size> to 0 to achieve what I want.
You are right, the lightstreamer server seems to be configured to...
Hi,
I would like to ask if the lightstreamer vivace server has any message throughput limit by default and if so, where can I increase it. I am testing with a drawing pad example using html 5...