long time taken to call terms and condation interface
the time taken to call terms and condation interface is around 24 seconds and it's not acceptable.
the code used :
ExtractionsContext _ExtractionsContext = ContextHelper.CreateExtractionsContext();
var availableFields = _ExtractionsContext.GetValidContentFieldTypes(ReportTemplateTypes.TermsAndConditions);
var extractionRequest = new TermsAndConditionsExtractionRequest {
IdentifierList =
InstrumentIdentifierList.Create(
new[] { new InstrumentIdentifier {Identifier = SecurityCode, IdentifierType =type },
}, null, false),
ContentFieldNames = new[] {"Company Name","Currency Code","ISIN","Issue Price",
"Issuer Name","MIC List","MIC","SEDOL","SICC","SICC Sector Code","Ticker",
"Trading Symbol","Trading Status","Official Name","Operating MIC" ,"RIC"}
};
var extractionResult = _ExtractionsContext.ExtractWithNotes(extractionRequest);
var extractedRows = extractionResult.Contents;
urgent matter
Tagged:
0
Best Answer
-
@rshehata, 2 comments:
- The code above contains a call to get the valid content field types. Is its output actually used ? Considering that the extraction request that follows it contains a hard coded list of fields, it looks like the call to get the valid content field types is not required (except if its output is used later on, outside of the scope of the snippet above). Removing it would gain a little bit of time.
- 24 seconds is not an unexpected time for such a request. DSS is a product that focuses on breadth and depth of data, it is not a real time product tuned to deliver extremely short response times
Edit: add comment:
For our support teams to look at the specifics of your call, it would be of advantage if you could give us a job ID or extraction ID, client session ID and/or correlation ID. Using that they could investigate further to understand if the 24 seconds you observed might be due to a specific issue. The job and extraction IDs are related to the requests you make. The client session ID (which you set yourself) and correlation IDs (which you receive) are described in the diagnostics help page. See also this query on the client session ID.
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
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 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.9K Refinitiv Data Platform
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛