Timestamp delay between EMA Java based App and rmdstestclient when subscribing the same universe.

An EAAS client subscribed US stock data, 10K, using both rmdstestclient and EMA Java based App. One of his testing cases is to use printed timestamp to check if any delay between rmdstestclient and Java App in receiving the same streams. Hundreds of milliseconds delay has been identifed in Java App's output comparing with that of rmdstestclient. Can you have a look at attached code to see where to tune to get Java App close to rmdstestclient? Thanks.
Best Answer
-
Hello @Tony.Zhu_R,
I understand the situation and the concern, and sympathize that the custom Java code is likely creating the delay in processing that being observed.
However, this forum is dedicated for general questions and discussions of API usage.
To review the custom code, and to recommend what is likely to be a comprehensive set of changes is not possible in the framework of the discussion forum.
I can see several feasible ways to proceed to help the customer who has written the code:
- If the customer is on Premium Support, when they login into developer portal and go into EMA API area, they should have a Contact Premium Support button, and should be able to submit this query via Premium support channel
- If the customer is not part of Premium Support, but would like to be, the should contact their Refinitiv account management team who should be able to help them sign up for Premium Support.
- If the customer would like the project to be done for them, they should contact their Refintiiv account team to discuss Professional Services offerings and options for them.
I hope this information helps?
0
Answers
-
-
-
Code:eaas-code.zip, no dict files included as there is 512KB limit for file uploading here.
RIC list in '0#UNIVERSE.NB.xlsx', thanks.
0 -
In addition to resources provided by Zoya, I would like to point out that EMA is extremely powerful and flexible API, but not the fastest one - certainly not as fast as low level ETA, which is probably what rmdstestclient is written in.
If the primary need for the client is to have a lowest latency application, then please refer them to use the ETA API.
The attached client application is a complicated one. The latency might well be in the user application code.
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
- 615 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 中文论坛