Initial image with large number of instruments
A batch request has more than 1000 instruemnts as a stream (intrest after refresh TRUE), the initial request take 30+seconds (initial image) what possibilities are there to improve the performance of the initial request.
Best Answer
-
Hi @niz
Can you confirm if you mean 30+ seconds to receive all Initial images or just the 1st image?
The time taken to receive the responses will depend greatly on a number of factors, for example, your network, the load on the servers you are connecting to, the number of fields in the Initial Image etc.
In terms of improving the performance, a few suggestions which may help:
- Use a VIEW request to reduce the number of fields and thereby the amount of data being transmitted and processed
- If you are connecting to an ADS server, you could experiment with two OmmConsumers - each one connecting to different ADS?
- Try throttling the request into smaller batches - may help the API better balance its processing of incoming and outgoing messages
0
Answers
-
Thanks for the update.
The request is a batchview with bid/ask.The omm consumer instance is new. And the list of instruments could have some invalid ones or some that the user has no dacs permission to, so those will have their stream id, which seems to differ from the handle id returned on the onrefresh will that id be used to close each item? Since there is no need to listen for its updates. Also would the dictionary have an effect based on its type for example minimal.
0 -
Hi @niz
Please see my reply to your other questions which should address some of the points you raise above.
If you are not interested in Updates and only the initial image, then you should set InterestAfterRefresh to false so that the API automatically closes the stream for you, once it has provided the Refresh (or StatusMsg in case of invalid instrument/request)
consumer.registerClient(reqMsg.serviceName("DIRECT_FEED").name("IBM.N")
.interestAfterRefresh(false), appClient)0
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 中文论坛