Delayed ACKs from the websocket contributions API

fjemiolo

Hi,

We are contributing around 20k update messages every 30s to the websocket contribution endpoint (contrib-ws1-amers1.platform.refinitiv.com), however we are seeing the ACKs coming in very delayed, up to a point where it is not possible for us to utilize them for correct failover/retry logic as suggested here (https://community.developers.refinitiv.com/questions/114212/ab-side-failover-using-websockets-api-for-data-con.html).

From my basic measurements it appears that the throughput of the system is 8 times lower than what we are streaming. We are only getting around 2.5k ACKs every 30s. From the login response message the limit should be 20k messages/s (```"Elements":{"TRCE:MaxMessagesPerSecond":20000}```).

What could be the issue here? Is there anything that our Content Manager can do for us on your end (e.g. change some configuration values)? The 20k update messages as we see them are being successfully sent over the websocket to your endpoint every 30s.

Thank you!

wasin.w

Hello @fjemiolo

Based on this old Confirmation of Python WebSocket (directly to RCC) is good or not for our use case post, the maximum contributions per second of each connection type of RCC are as follows (as of 2021):

• RSSL connection (for RTSDK C++/Java): 20,000 updates per second
• WebSocket connection: 1000 updates per second

The RTSDK C/C++ or Java editions (EMA or ETA APIs) may be more suitable for your requirement (20k update messages every 30s) then the WebSocket API.

The WebSocket API is designed for easy to develop and support various programming languages via the standard WebSocket connection and JSON message format. While the RTSDK uses Refinitiv's proprietary TCP-based connection called RSSL. The RSSL connection encodes data in binary format which is highly optimized for data distribution more than a JSON string format in a WebSocket connection.

You can find more details in the following article and tutorials:

• Contributing your data to Refinitiv article
• ETA C++ Consumer - Posting data to Contribution Channel tutorial
• EMA C++ Consumer - Posting data to Contribution Channel tutorial
• ETA Java Tutorial - Posting data to Contributions Channel
• EMA Java Consumer - Posting data to Contribution Channel

About the RCC ack delay issue, the WebSocket API is the server-side API, so you can contact the RCC support team directly via https://my.refinitiv.com/content/mytr/en/helpandsupport.html website to verify the issue on their end.

Alternatively, you can reach out to your LSEG Account team and arrange a discussion with the RCC product team to discuss your requirements/options further - as there may be additional limits on the RCC infrastructure.