DSS .NET SDK performance issues - ondemand extract
We are trying to fetch EOD prices through on-demand extraction .NET SDK for more than 10k instruments.This takes 20+ minutes to complete which is almost 10 times longer than time taken while using http endpoint.
Is it to be expected or we can do something to speed it up. If you need more information, please let us know.
Regards
Mithun
Best Answer
-
From the code, you are using the ExtractWithNotes endpoint. Therefore, the response should contain extraction information. For example:
"Notes": [
"Extraction Services Version 13.3.41369 (50b192356928), Built Feb 3 2020 17:30:35\r\nHoliday Rollover of Universal Close Price waived.\r\nProcessing started at 03/19/2020 05:50:17.\r\nUser ID: 9008895\r\nExtraction ID: 424491044\r\nSchedule: _OnD_0x07065045ef517094 (ID = 0x07065045fba17094)\r\nInput List (2 items): _OnD_0x07065045ef517094 (ID = 07065045f4917094) Created: 03/19/2020 05:50:15 Last Modified: 03/19/2020 05:50:16\r\nSchedule Time: 03/19/2020 05:50:16\r\nReport Template (73 fields): _OnD_0x07065045ef517094 (ID = 0x07065045f0417094) Created: 03/19/2020 05:50:15 Last Modified: 03/19/2020 05:50:15\r\n(CSP,438516AC0,CPN) is inactive.\r\nColumn 'CIN Code' suppressed for lack of 'CIN Code' permission.\r\nProcessing completed successfully at 03/19/2020 05:50:18, taking 0.728 Secs.\r\nExtraction finished at 03/19/2020 05:50:18 UTC, with servers: x04A06, QSHC16 (0.3 secs), QSSHA1 (0.0 secs)\r\nUsage Summary for User 9008895, Client 65508, Template Type EOD Pricing\r\nBase Usage\r\n Instrument Instrument Terms Price\r\n Count Type Subtype Source Source\r\n------- ----------------------------------- ---------------------------- -------------- ----------------------------------------\r\n 1 Corporate N/A N/A\r\n 1 Equities N/A N/A\r\n-------\r\n 2 Total instruments charged.\r\n 0 Instruments with no reported data.\r\n=======\r\n 2 Instruments in the input list.\r\nNo TRPS complex usage to report -- 2 Instruments in the input list had no reported data.\r\n"
]From this information, you can compare the processing time between .NET and HTTP.
0
Answers
-
Hi @mithun.ghosh,
Could you share the snippet code for .Net SDK and request's body for http endpoint? So, I can try to replicate the issue?
0 -
Hi Veerapath,
Thanks for your prompt response.
Please find the .Net SDK code below and attribute list attached with this mail.
public ExtractionResult CreateAndRunEodPricingExtraction(
InstrumentIdentifier[] instrumentIdentifiers, string[] contentFieldNames)
{
//Create an on demand extraction, of type EndOfDayPricingExtractionRequest:
PremiumEndOfDayPricingExtractionRequest extractionEod = new PremiumEndOfDayPricingExtractionRequest
{
IdentifierList = InstrumentIdentifierList.Create(instrumentIdentifiers),
ContentFieldNames = contentFieldNames
};
//Run the extraction.
//This call is blocking, it returns when the extraction is completed:
return extractionsContext.ExtractWithNotes(extractionEod);
}
We have tried to fetch EOD prices through on-demand extraction with more than 8k instruments. But for the security reason we will not able to share the instrument list with you.
Find the sample one instrument list below :
Identifier Type, Identifier Code,BB_UNIQUE_ID
ISN,US0276XAA,COEK4854
0 -
Hi @mithun.ghosh,
The ExtractWithNotes() function you are using with the .Net SDK will return when extraction is completed and data is received. Whereas the ExtractWithNotes HTTP endpoint uses Asynchronous mechanism which will return 202 status with Location URL if the request takes too long to process. Application needs to poll the location URL to get data when the extraction is completed.
Could you please confirm whether the time you get data with HTTP endpoint is 10 times faster than .Net SDK?
Also, as suggestion by Jirapongse, you can compare the Note information generated by .Net SDK and HTTP endpont. The Note information contains the time when extraction is started and completed.
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 中文论坛