Pause/resume and decreasing the frequency of updates coming from an ADS.

Hi,

I have an ommConsumer that registers its interests and receives updates from the server. Sometimes the rate of updates is too high and I would like to either pause/resume or decrease the update rate. Is it possible at all? I am using Java and would be useful to see an example/code-snippet in case it would really be possible to slow down the update rate and pause/resume the updates.

Many Thanks.

Find more posts tagged with

ommconsumer

pandas

Accepted answers

zoya faberov

Hello @AMofidy-Rouhi,

The rate of updates is set at the service level on the infrastructure. In can be every tick (TickByTick), it can be conflated. Would like to suggest to contact your market data group/admin to verify if an alternative conflated service is available to you.

I am guessing that the application may not be processing the updates quickly enough, and is being disconnected as a slow consumer. If this is the case, a couple of suggestions that may be helpful:

Threading- once the update is received, any heavy processing or interaction with external systems that requires wait should be handled by worker threads, outside of the callback.
Horizonal scaling can be used - see EMA Java example ex410_MP_HorizontalScaling
If your subscription instrument list is large - you may need to increase GuaranteedOutputBuffer parameter to accommodate your list, see EMA Configuration Guide for details, for example:

<GuaranteedOutputBuffers value="5000"/>

If significant number of the updates is not required, in receipt- do not process them further
If the market data is required infrequently, consider periodic snapshot instead of a continuous stream, see EMA Java example ex102_MP_Snapshot

Pause/resume can be requested, if supported by your infra, but not when application is being identified as slow consumer, for more information, see section Reissue Requests and Pause/Resume in RDM Usage Guide and example EMA Java ex350_MP_PauseAll.

Hope this information helps

All comments

zoya faberov

Hello @AMofidy-Rouhi,

I am guessing that the application may not be processing the updates quickly enough, and is being disconnected as a slow consumer. If this is the case, a couple of suggestions that may be helpful:

Threading- once the update is received, any heavy processing or interaction with external systems that requires wait should be handled by worker threads, outside of the callback.
Horizonal scaling can be used - see EMA Java example ex410_MP_HorizontalScaling
If your subscription instrument list is large - you may need to increase GuaranteedOutputBuffer parameter to accommodate your list, see EMA Configuration Guide for details, for example:

<GuaranteedOutputBuffers value="5000"/>

If significant number of the updates is not required, in receipt- do not process them further
If the market data is required infrequently, consider periodic snapshot instead of a continuous stream, see EMA Java example ex102_MP_Snapshot

Hope this information helps

Jirapongse

@AMofidy-Rouhi

You may consider using the dynamic view to only subscribe to the required fields. This can reduce the number of updates and the size of messages.

You can refer to the ex360_MP_View example in the RTSDK package.

However, the server must support this feature.

EXPLORE OUR SITES