For the elektron websocket api what is the maximum number of messages that will be received per seco
Best Answer
-
Hi @vikas.khurana,
To determine if you are connected to RTO or not - you can refer to the 3 Websocket API QuickStart sections and compare your credentials/connectivity parameters and service name with the ones used in the 3 different Quick Starts.
So, say you are consuming data from a service call ELEKTRON_DD and providing a MachineID + password + clientID/AppKey - then you are using RTO.
RTO is already using conflation / Bandwidth optimisation to limit the number of updates to 3 + Trades (as generally speaking most customers do not wish to miss Trade activity).
If you are connecting to your organisation's ADS then you won't be providing a password. If you are using an ADS you need to discuss conflation with your own internal MarketData team.
In terms of how many updates Websocket connection can support - we recommend customers perform their own testing within their own environments with their own watchlist.
This is because the actual number of updates your application can handle can vary based on factors such as your network/internet connection, your watchlist size, the volatility of the instruments in your watchlist, the typical size of the updates, the language you are using, how much processing you do to the payload on the same thread that receives the payload etc. If your application consumes the data too slowly, the server will eventually disconnect you once its buffer (for your session) is filled.
0
Answers
-
Hi @vikas.khurana ,
you can refer to this answer: https://community.developers.refinitiv.com/questions/74070/websocket-api-do-we-have-any-limitation-on-the-req.html
0 -
In terms of maximum messages received per second, this can vary quite considerably depending on the volatility of your instruments, any conflation on the feed/service you are connecting to etc.
For example, if you are connecting to our Real-Time Optimised feed, this provides 3 Updates per second + any trades. So, you could get 3 or more updates per second per instrument - depending on how actively the instrument is being traded. If the instrument is not quoted or traded that often you may get less than 3 updates per second.
If you are connecting to an internal ADS server at your organisation, then you will need to check with your Market Data team to check if the service is conflated or not. If not conflated, you could far more than 3+ updates a second - depending on how actively the instrument is quoted + traded, as explained above.
0 -
I'm mostly trying to understand what a good upper bound is on the number messages/second a single websocket session can handle. My assumption is that its the Real-Time Optimized feed but how do I confirm that? Also, how do look into the the potential conflation of the feed/service?
0 -
My assumption is that its the Real-Time Optimized feed but how do I confirm that? Also, how do look into the the potential conflation of the feed/service?
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 中文论坛