Content Comparison

...

The following example illustrates conflation for a single instrument with multiple updates.

Example 2 - Multiple Updates for Multiple Instruments - BrokerTec Markets

The following example illustrates conflation with multiple updates and multiple instruments.

Example 3 - Event Exceeds Conflation Interval - EBS Market

In this example, a market data event exceeds the 50 millisecond conflation interval. When the conflation interval is exceeded due to additional processing, MDP 3.0 waits until the event is complete before publishing messages.

Example 4 - No Messages within Configured Interval - EBS Market

In this example, there is no activity within the 50 millisecond interval. Therefore, MDP 3.0 resets the conflation interval to 50 and waits to publish the next market event.

Example 5 - Non-Conflated Message Flush - BrokerTec Markets

In this example, a non-conflated message is triggered, which causes the conflated data to be sent earlier.

Example 6 - Market Data Channel Reset with Conflation - EBS Market

Conflated EBS Market market data feeds support Market Data Channel Reset (tag 269-MDEntryType=J). Market Data MDP 3.0 - Channel Reset provides a process for synchronizing order books and trade session statistics in the unlikely event of a CME Group component failure. In this scenario, order books on the channel may be corrupted. During a conflation channel reset, Market by Price (MBP) messages will be sent down the incremental feed real-time.

The following diagram shows an example of a Market Data Channel Reset and Recovery for a channel with 2 instruments.