When is pause / resume more efficient then stop?
I am planning to have requests with interest open for many items.
I expect for high volume / high popularity items the streams will remain open most (if not all) day and likely will not be paused or uninitialized (specifically Level 1 and Level 2 Market Data).
However, I would like to optimize streams for less popular items so I do no stream data that is not being requested by users.
Would pause/resume be the right approach to take for these less popular items that will not require all day long open streams? At what point is pause/resume less efficient then simply uninitializing the stream for particular items followed by new request to stream with interest?
On a similar note, how long is it acceptable to pause items for? Seconds, Minutes, Hours etc before you should uninitialize the paused stream?
Best Answer
-
Hi @mzmuda33,
When a stream is paused, the updates are not delivered to the application by the infrastructure, but the last mile infra components continue to receive the data from the headend. This is useful when immediate lowest latency start of the stream is required.
In the absence of the paused stream, a new request is sent upstream to the headend (if it is not in cache already), which can add a bit of time (hundreds of milliseconds), before the data start flowing for that item.
You will have to prototype and see what option works best in your use case, but I think need-based subscription to an item should work fine.
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 中文论坛