One instance of the OnixS::CME::ConflatedUDP::Handler processes market data for a single channel only. Users must create multiple instances of the Handler to process data from multiple channels.
Filtering (instrument selection) is useful when market data required for specific instruments only. Instrument selection is like an inclusive white-list. E.g., if security A is selected, security-related events (members of OnixS::CME::ConflatedUDP::SecurityListener) are raised for security A only.
If two or more securities are selected, events are triggered only for those securities.
The Handler reports all errors and warnings through OnixS::CME::ConflatedUDP::HandlerListener::onError and OnixS::CME::ConflatedUDP::HandlerListener::onWarning callbacks respectively.
Any OnixS::CME::ConflatedUDP::SecurityListener::onBookUpdate call gives you consistent order book state (except for Natural Refresh mode). If you need book state at startup, you can just get a snapshot at first call.
It is a bit more complicated with book consistency & up-to-date. Please, note that CME does not guarantee 100% book up-to-date on intermediate updates. It is guaranteed only after 'End of XXX quote' market event where XXX is real. So you have to check this field to ensure the book is 100% up-to-date.
It can be achieved by using book update callbacks of OnixS::CME::ConflatedUDP::SecurityListener rather than atomic book update listening. They are publishing the books only on 'End of XXX quotes' market event giving guarantee books are consistent and up-to-date.
Book Atomic Update (OnixS::CME::ConflatedUDP::SecurityListener::onBookAtomicUpdate) is an elementary action over a book, and usually, there're multiple atomic updates inside a single snapshot or incremental refresh. Also, the book may not be valid between two atomic updates. Only when all atomic updates are processed from the single market event, the book is considered as valid.
Book Update (OnixS::CME::ConflatedUDP::SecurityListener::onBookUpdate) are raised exactly at a time when all atomic updates are processed, and the book appears to be valid and up-to-date.
Previously, all atomic updates were sent by the MDP within a single message. Therefore, there was correspondence between the updated book and the message that caused the book update. For that reason, order book updates were raised by the Handler at the end of single message processing. The SDK exposed the ability to obtain an instance of the message caused book update through the order book class interfaces.
The concept has been changed since MDP 3.0. The relation between the updated book and the message caused that update was eliminated. Order book updates are now raised at the end of the market (sub-) event like 'End Of Quotes' and 'End of Event'. In general, a single market event may consist of multiple messages. As a result, data referring to a single book update may be distributed across multiple messages.
Also, the MDP assigns sequence numbers to the packets, but not to the messages. Previously, each packet sent by the MDP consisted of a single message. Thus messages could be identified by the sequence number of the packet containing the message. Therefore, the SDK exposed sequence number attribute for the messages.
Since the MDP 3.0, a single packet may include multiple messages. Therefore, the sequence number attribute was removed from the SDK classes encapsulating messages. Instead, the SDK exposes the new class representing the packet.
Finally, the attribute identifying the end of the market event is sent in the messages. As far as a single packet may contain multiple messages, multiple market events may be sent within a single packet. Thus multiple order book updates may be raised while processing a single packet.
Security definition sent by Market Data Platform contains fields
representing the multipliers to convert the CME Globex display price to the conventional price.
When the Handler performs book recovery, it caches all the data received on incremental feeds. When the market is busy, a number of cached messages may exceed configured limit defined by the OnixS::CME::ConflatedUDP::HandlerSettings::recoveryQueueMaxSize parameter value. So, to avoid
QueueOverflow warnings, it is necessary to increase the value of the noted parameter.
The cause is a violation of received packets sequence (gap) that wasn't restored after the OnixS::CME::ConflatedUDP::RealtimeFeedSettings::outOfOrderPacketMaxInterval number of packets or after the OnixS::CME::ConflatedUDP::HandlerSettings::lostPacketWaitTime elapsed. Violation of packet sequence can be caused by packets loss on different levels: CME environment issues, network connectivity issues, system or application issues.
Also, when Handler performs a large-scale recovery due to the gap or while joining market lately, incremental packets are cached. In case of intensive data transmission, queue keeping incremental packets may reach its limit causing a noted warning.
Please refer to our Lost multicast packets troubleshooting guide for more details.
The Handler allows tracing packets as they are received by active feeds including out-of-order or duplicated packets (in contrast to market data listening which exposes packets passed through session rules). With the help of the new OnixS::CME::ConflatedUDP::FeedListener listener, it is possible to write advanced diagnostic services.
The Benchmarking Results topic contains results of latency measuring.
It depends significantly on many different parameters including network, hardware, operating system environment, market data rate and applied handler settings.
The smaller, the better. It shall be as small as possible to do not impact the ability to process data on high tickers. Although the Handler and the Feed Engines use different techniques to avoid data losses during data bursts, long callback execution may lead to buffer overflows and thus data losses.