OMM Provider settings to avoid RSSL buffer failures
We have a high throughput provider application that from time to time disconnects after an OMM Error "Attempt to get rssl buffer failed" is triggered. From what we understand, this can occur when there are issues sending data between the provider and the ADH (network blip, capacity issues, ...).
We increased \Connections\<conn>\guaranteedOutputBuffers to 10000.
a) Apart from the information in the RFA Config Guide, is there any guidance for setting connection parameter values?
b) Should maxOutputBuffers be increased to a similar value to the guaranteed buffers?
c) What value do recvBufferSize/sendBufferSize take when not defined (what is the default size)?
d) What is the impact of setting disconnectOnGetSubmitBufFailed to false (does it block/drop message)?
We are using the RFA 8.1.0 C++ sdk.
Best Answer
-
Hi @sbutler9
Yes, you can also increase maxOutputBuffers - values as high as 20,480 (for both this and guaranteedOutputBuffers) is not unreasonable.
The default value for the recv and send buffers will be specific your local PC/Server environment.
Setting disconnectOnGetSubmitBufFailed would result in the connection being dropped if RFA fails to get enough buffers for submitting messages.
0
Answers
-
Apart from the information in the RFA Config Guide, is there any guidance for setting connection parameter values?
0 -
Hi @sbutler9
Unfortunately not - as their are too many factors at play including but not limited to things like instrument volatility, update rates, update sizes - your TREP config, your network etc etc.
It is a case of trial and error to arrive at works best for your situation.
You can also try increasing the number of guaranteedOutputBuffers and maxOutputBuffers on the ADH - it may be enough to get you past some short periods where you are publishing at higher rate than average.
You can also use the throughput and latency testing tools that come with our TREP packages to perform load testing.
1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛