Recommendation with using the https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/Ex...

...tractWithNotes without taking so much time
I am trying to download reference history for futures option contracts. I was using this REST API:
https://selectapi.datascope.refinitiv.com/RestApi/v1/Search/ReferenceHistory
It was recommended that I change to use https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotes with
DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest.
This new method is much better, the data is far superior.
However, this new method is very, very slow. With the old method an expansion of the rich chain takes less than one minute.
With the new method it takes 10's of minutes, if not hours. I am wondering if I am doing something wrong or if there is a problem at the LSEG end?
I have attached a sample request and reply file.
Here is the notes file:
Extraction Services Version 18.2.1.47729 (1e1acc120e4a), Built Sep 25 2024 21:21:17
Processing started at 23-10-2024 14:04:49.
User ID: 9035975
Extraction ID: 2000000803232870
Correlation ID: CiD/9035975/AAAAAA.0922cfa6546a86df/RA
Schedule: 0x0922cfa6552a86df (ID = 0x0000000000000000)
Input List (7332 items): (ID = 0x0922cfa6552a86df) Created: 23-10-2024 14:04:49 Last Modified: 23-10-2024 14:04:49
Report Template (34 fields): _OnD_0x0922cfa6552a86df (ID = 0x0922cfa6556a86df) Created: 23-10-2024 12:44:06 Last Modified: 23-10-2024 12:44:06
Schedule dispatched via message queue (0x0922cfa6552a86df)
Schedule Time: 23-10-2024 12:44:24
Historical Reference Date Range: 21-10-2024 to 21-10-2024
Processing completed successfully at 23-10-2024 14:10:20, taking 331.317 Secs.
Extraction finished at 23-10-2024 14:10:20 UTC, with servers: xc38bxzyq14, DHS (134.8 secs), QSDHA1 (0.0 secs), QSHC02 (184.4 secs)
As you can see the processing was only 5 minutes but the start/completion times indicate 1h 26m for the request.
I would like to use this method but with 235 chains to expand the processing times are excessive.
Best Answer
-
Thank you for reaching out to us.
There are many factors that can impact extraction times, such as the number of instruments, the number of fields, date range, the number of data, and server load.
Please check the Best Practices & Fair Usage Policy for LSEG DataScope Select and LSEG Tick History guide for more information.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 689 Datastream
- 1.4K DSS
- 627 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 278 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 708 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛