[This message was posted by Anders Furuhed of Pantor Engineering <[EMAIL PROTECTED]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/6f61965f - PLEASE DO NOT REPLY BY MAIL.]
> Hi, everyone, > > what are the expectations for the FAST encoder and decoder with respect > to CPU utilization? My implementation encodes approximately 90K+ > messages per second and decodes 120K+ messages per second, with > compression ratio of 3x (for Level2 data). > > However, the bad news is that Fast decoder uses more CPU than its non- > FAST peer, and the gap widens at higher rates. At 50K messages per > second, FAST utiliizes over 2x of CPU (20% compared to 10%). > > Is this really expected? I was hoping that since less data travels over > the network, the CPU utilization would be comparable (as latency is). > > Thanks, Dimitry Dimitry, the difference in message layout, e.g., the use of fewer and larger MarketDataIncrementalRefresh with multiple internal entries in contrast with a feed using more but smaller messages, makes it hard to make comparison between feeds on a messages per second level. One option is to measure cpu use vs fields per second or FAST encoded bits per second, both as a way of comparing implementations. Using bits per second also makes it possible to compare processing complexity for different feeds. I think that we have measured a factor of about five in messages per second decoded depending on what data set is used. Also, we have seen a factor of five to ten in encoder/decoder performance comparing the original FAST 1.0 sample code to more heavily optimized implementations. Cheers, Anders [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
