question

Upvotes
Accepted
1 1 2 2

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.

elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-apijava
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
Accepted
28.3k 30 11 15

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?


premiumsupport.gif (21.8 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1 1 2 2

eaas-code.zip (138.2 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1 1 2 2

0universenbxlsx.zip (64.1 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1 1 2 2

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.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
14.7k 39 12 18

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.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.