RFA API behavior when application thread is blocked during market Data processing
Hello, we are using the RFA 8.2 C++ API to consume market data. In our application, the Driver Thread utilizes the RFA libraries to request data and receive callbacks from TREP through a TCP connection. If the Driver Thread becomes blocked and is unable to process incoming data, will the RFA libraries continue to receive and buffer data until the Driver Thread can resume processing, or will they stop receiving data from TREP if the Driver Thread is blocked? What is the expected behavior in this situation?
Best Answer
-
Hello @mktdata,
The application behavior will depend on the data load on the application. There are internal buffers within the SDK and RTMDS which will start filling up, if the app thread does not empty the received messages fast enough. If this continues for too long, these buffers will eventually overflow, and the infrastructure will disconnect the offending consumer app.
This scenario is called a slow consumer.
If however, the data update rate is low, and the driver thread is blocked rarely, the inbuilt buffers should be able to handle this temporary disruption.
0
Answers
-
The buffers in the RFA and the RTMDS are configurable. You can read about these parameters in the RFA configuration and logging guide, packaged with the SDK. Your market data admin should be able to configure the buffers on the infrastructure side.
Important thing to note is that - if the consumer is really slow and unable to process messages fast enough, then no amount of buffers can fix this situation. Having very large buffers will increase the latency in the application update rate, and the consumer will disconnect after a bit of time anyways.
0 -
Thank you for reaching out to us.
It depends on the thread model that you are using. Please check the section 17.4 Configuring the RFA Consumer for Performance in the RFA developer guide.
If the application uses Single Threaded With an Event Queue (Client Model), a RFA thread will push events in to an event queue while an application thread is busy or blocked.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 616 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛