The conflation mechanism in RTO, 3 updates per second?
May I know the conflation mechanism for the RTO?
It's described as 'all trades and 3 updates per second for quotes'.
So how to do the conflation for 3 updates per second? every 1/3 second it will generate a quote update? or 3 quote update at most for a second? what's the conflation logic on that?
Best Answer
-
Hi @Frederic
With the RTO conflation, you should receive all Trade events.
It is also possible for a quote update to be combined with a trading update.
For quotes, if there have been any quotes in the past1/3 second, they would be conflated into a single quote update. If there has been no market activity on that instrument in the past 1/3 second you should not receive an update.
For example, below I subscribed to STAN.L for just over 60s from RTO:
Stats; Refresh: 0 Updates: 0 Status: 0 Pings: 0 Elapsed Time: 0.00secs
Stats; Refresh: 1 Updates: 1 Status: 1 Pings: 0 Elapsed Time: 5.02secs
Stats; Refresh: 1 Updates: 8 Status: 1 Pings: 0 Elapsed Time: 10.05secs
Stats; Refresh: 1 Updates: 23 Status: 1 Pings: 0 Elapsed Time: 15.09secs
Stats; Refresh: 1 Updates: 26 Status: 1 Pings: 1 Elapsed Time: 20.13secs
Stats; Refresh: 1 Updates: 26 Status: 1 Pings: 1 Elapsed Time: 25.15secs
Stats; Refresh: 1 Updates: 27 Status: 1 Pings: 1 Elapsed Time: 30.19secs
Stats; Refresh: 1 Updates: 30 Status: 1 Pings: 1 Elapsed Time: 35.24secs
Stats; Refresh: 1 Updates: 32 Status: 1 Pings: 2 Elapsed Time: 40.26secs
Stats; Refresh: 1 Updates: 53 Status: 1 Pings: 2 Elapsed Time: 45.33secs
Stats; Refresh: 1 Updates: 55 Status: 1 Pings: 2 Elapsed Time: 50.38secs
Stats; Refresh: 1 Updates: 55 Status: 1 Pings: 2 Elapsed Time: 55.44secs
Stats; Refresh: 1 Updates: 56 Status: 1 Pings: 3 Elapsed Time: 60.48secs
Stats; Refresh: 1 Updates: 94 Status: 1 Pings: 3 Elapsed Time: 65.53secsAs you can see:
in the 10-15 sec time window, I received 15 updates = 3 per second.
in the 20-25 sec time window, I received 0 updates.
in the 5-65 sec time window, I received 93 updates - an average of 1.5 updates a second.1
Answers
-
The conflation is done by RTO server side or EMA application side? And if this goes to the LPC in the scenario, will the conflation be done by LPC?
0 -
Conflation is done by RTO servers.0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛