RT-O Channel down when number of RICs subscribed
Hi
My customer is suffering channel down when they subscribe around 5000 RICs on one application.
Program Language - Java
RTSDK Java edition (EMA) is being used.
We are using sample code ( ex450_MP_QueryServiceDiscovery.Consumer )
The channel down can not be replicated on our desktop, so we are assuming the client network or PC may have some kind of limitation.
However the rate of disconnection can be reduced depends on the number of RICs reduced.
So we compared the disconnection rate in between bellow two cases.
Case 1 : 1 app ( 1 session ) with 5000 RICs -> this resulted channel down happened in every 10-15 minutes during market hours.
Case 2 : Multiple apps with less than 1000 RICs ( total RIC number is same as Case 1 ) -> the channel down was still hapenenig but the rate of down was siginifiantly lower than Case 1.
Both test case, same total 5000 RICs are subscribing, so the load of network and machine CPU usage should be also same but we are wondering how come Case 2 is quite less rate than Case 1.
I would like to ask if there can be any parameter on Java RTSDK to optimize for many of RICs to suvscribe ? Wising to reduce the rate of channel down even 5000 RICs subscribed on One application.
Best Answer
-
They are getting disconnects in both the cases - so it is hard to quantify that one works and other does not.
When multiple applications connect to RTO, they are most likely serviced by a different physical endpoint. So they all are likely getting data from a different server (even when the service discovery endpoint is same). Some of these servers might be less tolerant of how much backlog of data it keeps before kicking the application out.
The client should fix the underlying problem of high latency and low bandwidth. You can also recommend them to move their application to the cloud - closer to the source of the data.
0
Answers
-
RTSDK Java should easily handle a batch of 5K instruments. If you are getting a channel down event, it points to a network bandwidth issue.
What is the channel type and protocol that the client is using? They can use the view feature to reduce the number of FIDs they receive in the update message - which should reduce the bandwidth usage.
0 -
Hi @Gurpreet
Many thanks for your comment. Yes I also believe 5K RICs should be able to handle as well.
Question here is that how come the customer sees different outcome between cases, a: which is 5K x 1 session and b:1K x 5 sessions ( actually using 5 different Machine IDs ). From network point of view. Both cases , they should receive same volume of data, thus Network bandwidth may not be the simple bottleneck?
Please note I also asked the customer to consider to use VIEW featue and it is under discussion within the developpers in the custiomer.
Thank you
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 中文论坛