[This message was posted by Greg Orsini of JetTek, LLC <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/827879d1 - PLEASE DO NOT REPLY BY MAIL.]
> What are your experiences and thoughts about Orc Cameron VS Appia? Comparisons such as these are somewhat difficult in the abstract. It is usually better to try a bake-off between the engines you are considering. That way, you can measure performance in your own environment and configuration (e.g., linux using TIB/RV) as the specific OS, middleware, and topology (in-process, out-of-process) are important elements. The commercial vendors will typically help you with this benchmarking exercise by providing target performance figures on your OS and similar hardware and usually offer advice if you are coming in far short of the target. Things to look for during this sort of evaluation: 1. logging - vendors tend to turn off message logging as it slows things down. 2. validation - turned on or off? what is your requirement? 3. message persistence - inbound and outbound message persistence or sequence number persistence (since the engine is responsible to replay messages to the counter-party, it stores them internally). 4. asynchronous message persistence and batching. This can lead to vulnerability to message loss in case of abnormal program termination or other failure. 5. message object creation. In benchmarks, it is common to use the same message object and send it repeatedly. If your application will generate new message objects, then this benchmark is not realistic (hides GC effects). 6. bidirectional message flow. Inbound traffic can hamper outbound performance, so even if you are focused on outbound latency, you may want to include inbound traffic in your analysis. 7. outliers. Average latency and speed is important, but so is the worst latency and speed. Although I've tried to be product neutral, full disclosure: my company sells performance add-ons for CameronFIX, among other tools. Cheers, Greg. [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.
