Bandwidth and event pushing

[Mone]

Hi,

You wrote another post while I was writing the response for the previous one

In the new log you can see how the merge algorithm works when different items are used:

08.May.07 09:56:57,239 <TRACE> INCOMING DATA for EUR/GBP --> {bidValue=0.3952132682553846, sellCCY=GBP, bidCCY=EUR, sellValue=0.1582634326389245}
08.May.07 09:56:57,338 <TRACE> INCOMING DATA for EUR/USD --> {bidValue=0.9052316638725739, sellCCY=USD, bidCCY=EUR, sellValue=0.47263148734258653}
08.May.07 09:56:57,339 <TRACE> INCOMING DATA for EUR/GBP --> {bidValue=0.7117531450899011, sellCCY=GBP, bidCCY=EUR, sellValue=0.5475364773823609}
08.May.07 09:56:57,340 <TRACE> INCOMING DATA for USD/NZD --> {bidValue=0.3461941736979528, sellCCY=NZD, bidCCY=USD, sellValue=0.19362361881184487}
08.May.07 09:56:57,439 <TRACE> INCOMING DATA for EUR/USD --> {bidValue=0.7626206088735283, sellCCY=USD, bidCCY=EUR, sellValue=0.5145519477153373}
08.May.07 09:56:57,440 <TRACE> INCOMING DATA for JPY/USD --> {bidValue=0.204416519895124, sellCCY=USD, bidCCY=JPY, sellValue=0.2764089416286716}
08.May.07 09:56:57,440 <TRACE> INCOMING DATA for EUR/GBP --> {bidValue=0.5949231423651182, sellCCY=GBP, bidCCY=EUR, sellValue=0.5972830556785825}
08.May.07 09:56:57,450 <TRACE> Pumping event in session S-725498679N1: 4,1,1||0.7626206088735283||0.5145519477153373
3,1,1||0.5949231423651182||0.5972830556785825
6,1,1|USD|0.3461941736979528|NZD|0.19362361881184487
2,1,1||0.204416519895124||0.2764089416286716

Inside this 200ms you can see that the server accumulated 7 events but 4 are sent to the client. If you look further you can see that those 7 updates pertains to only 4 items because there are 3 EUR/GBP and 2 EUR/USD events so that the server to send the latest update per each item have to send only 4 updates.

Hope that helps.

[churrusco]

Absolutely it helps, and it makes quite a lot of sense indeed. Great feature and quite easy to configure. Actually it was my fault haven't re-read the documentation. I read it one or two months ago and almost forgot everything about these modes. I believe it has to do with the age

Happily enough the simulation is now working fine so I can start stressing it Also I would like to comment some minor things:

- I found that with the RAW mode the server log messages are weird as it seems as if Lighstreamer was throttling messages. But the reality is that all of them arrive at the client even when in the logs it seems that only one is pushed. See attached file.

- I also see that there is a timeout and the session is maintained idle for 30 seconds. I guess this feature is to optimize AJAX communication, isn't it? (I say it because we are targeting an Applet environment so our ideal is just a "0" timeout with no back buttons and this browser stuff.)

Cheers,
Martin

[churrusco]

Hi Mone,

Just forget the first minor issue. I just have realized the obvious, that there are different pump threads and this is not a sequential process

Cheers,
Martin

[Mone]

The session is kept open for some time.
There is a set of session configurations that you can tune to let Lightstreamer behave as you desire.

If you have the original (i.e. the one in the distributed zip) Lightstreamer_conf.xml file you will see an entire section called "SESSION CONFIGURATION".
Read the comments inside it to have an overview of the session handling.

Feel free to ask if something is unclear.

[churrusco]

Thanks a million. You've been very helpful.

Martin