Pause/resume and decreasing the frequency of updates coming from an ADS.
Hi,
I have an ommConsumer that registers its interests and receives updates from the server. Sometimes the rate of updates is too high and I would like to either pause/resume or decrease the update rate. Is it possible at all? I am using Java and would be useful to see an example/code-snippet in case it would really be possible to slow down the update rate and pause/resume the updates.
Many Thanks.
Best Answer
-
Hello @AMofidy-Rouhi,
The rate of updates is set at the service level on the infrastructure. In can be every tick (TickByTick), it can be conflated. Would like to suggest to contact your market data group/admin to verify if an alternative conflated service is available to you.
I am guessing that the application may not be processing the updates quickly enough, and is being disconnected as a slow consumer. If this is the case, a couple of suggestions that may be helpful:
- Threading- once the update is received, any heavy processing or interaction with external systems that requires wait should be handled by worker threads, outside of the callback.
- Horizonal scaling can be used - see EMA Java example ex410_MP_HorizontalScaling
- If your subscription instrument list is large - you may need to increase GuaranteedOutputBuffer parameter to accommodate your list, see EMA Configuration Guide for details, for example:
<GuaranteedOutputBuffers value="5000"/>
- If significant number of the updates is not required, in receipt- do not process them further
- If the market data is required infrequently, consider periodic snapshot instead of a continuous stream, see EMA Java example ex102_MP_Snapshot
Pause/resume can be requested, if supported by your infra, but not when application is being identified as slow consumer, for more information, see section Reissue Requests and Pause/Resume in RDM Usage Guide and example EMA Java ex350_MP_PauseAll.
Hope this information helps
1
Answers
-
You may consider using the dynamic view to only subscribe to the required fields. This can reduce the number of updates and the size of messages.
You can refer to the ex360_MP_View example in the RTSDK package.
However, the server must support this feature.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛