We are pulling both realtime and delayed data using .NET API but experiencing serious delays or timeouts on responses for the delayed RICs when market is busy. How does Refinitiv handle priority for these requests?
Hi @dave.1 ,
The answer to your question is very specific to how your market data infrastructure is setup. Within the RTDS, there is no specific mechanism to give priority access to one instrument compared to another. What is the source of your delayed data - are you subscribing to delayed RIC's from headend or is the data being delayed in your environment. It might also happen that your ADS is configured to cache the realtime instruments.
All this information can be provided by your market data administrator, who can also look at why certain RIC's take a long time to process.
Hi @ralphh,
What .NET APi are you using. Are you connecting to your local (inhouse) market data system. How many concurrent instruments does your app subscribe to?
At the moment this is a general question about how delayed RICs are handled compared to real-time. Yes our app is connecting to a local TREP with approx. 10,000 delayed instruments. Is it possible that for a response to delayed RICs will be up to 20-30 seconds or more? We understand there are several variables but if that is possible, under what conditions such delays are likely to occur? we know that delayed RICs have a lower priority but is there any guideline?
Do you know if the TREP has any logs which report on such delays in responses.
