tickhistory data extraction time

One of clients is interested in TickHistory time and sales data for FX such as NOKSEK= and SEKJPY=R.
They would like to know the following points:
- If they would like to extract 5 year history, what would be the best chunk to recommend to retrieve the tick data? e.g. 1 year or 5 year? I understand that in Best Practice Guide, user should “disperse requests instead of submitting a large set of requests at once. Submitting large sets of requests simultaneously can impede system performance. Please disperse your requests within the defined limits and only submit the requests that you need.” Can they just extract the data of 5 years as one go, as this very small set of 1 or 2 RICs?
- How long would it take to retrieve the tick data (from request until download) as recommended time frame in question (1)? I understand that it would depend on client technical environment, but if you have any typical example of extraction time, it would be great.
Regards,
Hiroko
Best Answer
-
Thank you for reaching out to us.
There are many factors that can impact the extraction and download times.
I have tested several cases by using TickHistoryTimeAndSalesExtractionRequest to extract "Quote - Ask Price", and "Quote - Bid Price".
The results are:
SEKJPY=R is more active than NOKSEK= so it takes more time to extract and download the data.
Users can use an extraction request to extract all data in one go. However, it will take a long time to extract and dowload a file. This method is suitable for the backend or unresponsive applications.
For responsive applications, users can split it to multiple requests, such as one request for one year data.
Moreover, according to the Best Practices guide, users can run two requests concurrently. This can speed up the overalll processes.
The number of concurrent extractions that can be processed on a per-report and per-user basis is two for all report templates except Intraday Pricing and Historical Reference report templates. ..
In addition, downloading files from the AWS is faster than downloading files from the DSS server. Moroever, users can speed up the downloads by concurrenlty download a file with the Range header, as mentioned on the Downloading a Large Tick History File with Python article.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 622 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛