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
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.