I have read in the best practice guide for DSS that an application will receive a 429 error if it makes too many requests. However, I cannot find any stated limit on the number of request that an application can have concurrently with the DSS API using a single user id. Is this limit known?
For a deeper look into our DataScope Select SOAP API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
20
●2 ●1 ●5
What is the limit on the maximum number of concurrent requests using the DSS API
13.7k
●26 ●8 ●12
@mark.ringrose, see attached dss-12-0-release-notes-apr2018.zip.
Here is the relevant extract:
In order to support consistent performance and optimize response times for the most users, DataScope Select now applies request execution limits and queuing on a per-template basis, which allows for more granular resource balancing. This is applied across all product interfaces: GUI, REST API, SOAP API, and FTP. The limits are:
50 concurrent requests per user per template, for each of the following templates:
- Commodities Corrections History
- Fund Allocation
- News Analytics
- News Analytics Commodities
- News Items
- Ownership
- StarMine
500 concurrent requests per user for the Intraday Pricing template.
If you reach the per-user limit on the number of extraction requests for that template, any additional extraction requests that you submit against that template will fail, with the extraction notes explaining why. (If submitted via the REST or SOAP API, it will also return status 429.)
In future releases, additional templates will support template-specific execution limits.
23k
●22 ●9 ●14
Hello @mark.ringrose,
It's been upgraded fairly recently, and for the majority of custom requests it's 50.
Please see the detailed overview Product Change Notification: New Processing Limits For Better Performance
1
●0 ●0 ●0
That answer is for Tick History Requests via DSS.
Do we know the limit for Legal Entity Data?
1
●0 ●1 ●3
Hi Christiaan,
I went through the Best Practices and limits documentation.
it is clear that the limit of concurrent requests for the below reports is 50. But how to find out for the limit number for the most used report such as intraday pricing, End of day pricing, or Terms and Conditions?
thanks and regards
Ludovic
50 concurrent requests per user per template, for each of the following templates:
- Commodities Corrections History
- Fund Allocation
- News Analytics
- News Analytics Commodities
- News Items
- Ownership
- StarMine
13.7k
●26 ●8 ●12
As stated in the accepted response, for Intraday it is 500 concurrent requests; this is mentioned in the DSS 12.0 Release Notes (RN).
For Price history it is 50 (since version 13.1), as stated in the DSS 13.1 RN on page 12.
I could not find the info for EoD and T&C, I'll investigate that and come back when I have a response.
84
●3 ●0 ●1
@ludovic.mesnier,@Christiaan Meihsl
Currently, Maximum Requests with Extractions or On Demand EOD or T&C would be 800 (time period 60 seconds). Thank you
1
●0 ●0 ●0
Hello, is it still the case that there are 500 concurrent requests per user for the Intraday Pricing template?
23k
●22 ●9 ●14
Hello @franco.grbac ,
Please refer to DataScope Select Best Practices & Fair Usage Policy.
Currently, 1500 is the limit to Intraday Pricing requests to be submitted
"You can submit a maximum of 50 concurrent requests per report template for all report types except Corporate Actions and Terms and Conditions (Maximum Concurrent Requests per Report Template = 500) and Intraday Pricing (Maximum Concurrent Requests per Report Template = 1500). "
Additionally, I find the limit of requests to be processed concurrently very important for the majority of requirements/solutions:
"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, Historical Reference, Elektron Timeseries report templates. Intraday Pricing supports concurrent extraction processing of up to 50 reports. Concurrent extraction processing is not supported for Historical Reference and Elektron Timeseries report templates. Any remaining user extraction requests remain in a Queued status." If your requirement is not to submit the requests just to be queued, as a solution architect you will find this also an important consideration. Whereas for some requirements, you do not mind the queuing.
