ema slow reader application
This is specific to a consumer app written using EMA c++ library.
What if the event handling code (i.e. code that handles refresh/update/status) messages is too slow to keep up with the tick rate?
Does ema has a internal queue where ticks are buffered or it directly invokes handler from the reader thread? Is there a way to configure?
Or the ticks would just be dropped (temporarily or permanently?).
Best Answer
-
In EMA, there is no internal queue where ticks are buffered. It uses the application thread (User Dispatch mode) or EMA thread (API Dispatch mode) to dispatch received messages. If the application delays in dispatching messages, it can result in slow consumer behavior.
When the consumer is slow, TCP receive buffer of the consumer side will be full. Therefore, the provider side can't send the data to the consumer.
The provider side has output buffers which hold the data before sending to the network. When the consumer is slow, the output buffers of the provide side will be depleted because it is unable to flush the data in the buffers to the network.
When the provider can't get the output buffer to write the data, it can decide what to do in this situation. For example, ADS (Advanced Distribution Server) will cut the connection. However, if Traffic Management is enabled in ADS, ADS will aggregate the data when output threshold is breach. Then, it will send the merged update when the buffer threshold is back to normal.
The market data traffic management algorithm in the ADS allows the ADS to slow down the stream of updates to a client application. Enabling this algorithm should significantly reduce the occurrence of channel disconnects due to buffer overflow at the cost of merging multiple update events for an instrument.
In both cases, Tick-by-Tick data will be lost.
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 中文论坛