Refinitiv Data API performs worse than Eikon on large universes
Hello. I've recently been looking at implementing the Refinitiv Data Library in existing code over the eikon library. I've found that when large universes are specified, the refinitiv data library performs significantly worse than the eikon library. Following some testing some strange results were found. For example:
When using the chain operator, the RD library performs better as expected. When requesting a large list of RICS, eikon performs better. If you pass these individually instead, RD once again performs significantly better. This has lead to some previously functioning code timing out, so what is the best way to deal with this. I don't know if this is expected, so what is the best way to handle requesting data for a large number of instruments. Thank you in advance.
Best Answer
-
Hi @ns02 ,
Both libraries are using the same underlying service for the request you have above, however, the service response times might be different for each request regardless of the library. I have run a query below for 100 RICs in a loop. See the code and results below:
Best regards,
Haykaz
0
Answers
-
Can you try with my example with a refreshed Kernel and the RD library first?
Here is the universe:universe = ['US3MT=RR', 'US2YT=RR', 'US5YT=RR', 'US10YT=RR',
'EU3MT=RR', 'EU2YT=RR', 'EU5YT=RR', 'EU10YT=RR',
'JP3MT=RR', 'JP2YT=RR', 'JP5YT=RR', 'JP10YT=RR',
'GB3MT=RR', 'GB2YT=RR', 'GB5YT=RR', 'GB10YT=RR',
'FR3MT=RR', 'FR2YT=RR', 'FR5YT=RR', 'FR10YT=RR',
'DE3MT=RR', 'DE2YT=RR', 'DE5YT=RR', 'DE10YT=RR']
fields = ['CF_NAME']
Many Thanks @aramyan.h
0 -
Hi @aramyan.h, Thank you for your reply. It turns out in my case, it looked like it was taking longer due to the longer first call of rd.get_data(). So in this case, it is true the rd library works better. I have looked into our code and found the function calls that took longer. I was able to replicate the phenomenon I was seeing like this:
0 -
With a similar to result if I use get_data instead.
0 -
Awesome, Thank you for the help!
0 -
0
-
still waiting the team to check, will update here0
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 中文论坛