Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Gliffy
imageAttachmentIdatt68780047att457094679
macroId271c72e7-979b-4d30-8656-9b4047c1bc27
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
displayNameMulti Updates for Single Instrument - BrokerTec
nameconflation_multi_updates3
diagramAttachmentIdatt68747286att457421136
containerId68452430457572870
version5
timestamp17443940839071744395637994

Example 2 - Multiple Updates for Multiple Instruments - BrokerTec Markets

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

Gliffy
imageAttachmentIdatt68780057att457572883
macroIdd2d28afe-e541-4e42-a666-3df76e715c16
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
displayNameMulti Updates for Multiple Instruments - BrokerTec
nameconflation-multi-instruments
diagramAttachmentIdatt68812817att457421089
containerId68452430457572870
version5
timestamp17443939181211744395671045

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.

Gliffy
imageAttachmentIdatt71467484att692355120
macroId62b92188-ab86-40b2-b9dd-f3f9cdff2773
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
displayNameconflation-past-interval - EBS
nameconflation-past-interval-1
diagramAttachmentIdatt71369326att692781093
containerId68452430457572870
version2
timestamp17441368268741744395691419

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.

Gliffy
imageAttachmentIdatt69501150att692453409
macroId2c0bcacb-a158-4d25-ae60-e37f8e7893ff
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
displayNameNo Messages within Configured Interval - EBS
nameexample 4
diagramAttachmentIdatt69501144att692289594
containerId68452430457572870
version2
timestamp17437148006491744395708358

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.

Gliffy
imageAttachmentIdatt68780120att457638309
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
macroIdde5a9979-39ba-4917-95ef-24d51dc084b9
displayNameNon Conflated Message Flush - BrokerTec
nameconflation-pass-thru
diagramAttachmentIdatt68812835att457638305
containerId68452430457572870
version3
timestamp1744395725803

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

...

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

Gliffy
imageAttachmentIdatt69468415att692650023
macroIdfb02a38c-4e42-42f2-abbf-4a2fb26f2742
baseUrlhttps://cmegroup-publicstagingcmegroupclientsite.atlassian.net/wiki
displayNameChannel Reset with Conflation - EBS
nameexample 6
diagramAttachmentIdatt69501191att692092981
containerId68452430457572870
version2
timestamp17437148882221744395741719