We’re using the PDF cloud API to upload, convert and download PDF files.
In the recent week(s), the performance of this API is very instable, resulting in some requests being handled normally (with a response within seconds), while others can take a minute or even longer to respond.
We use the following requests
- PUT on
https://api.aspose.cloud/v3.0/pdf/storage/file/{path}
- repeatedly GET on
https://api.aspose.cloud/v3.0/pdf/{file}/pages/{number}/convert/png
- DELETE on
https://api.aspose.cloud/v3.0/pdf/storage/folder/{path}
I created a script that performs these requests and measures the response time.
This proves that some calls take around a minute to succeed. Interesting in that respect is that normal response time is around 1 second and the requests that take longer are always at around 60 seconds + a little bit.
The script and an example PDF with 10 pages are attached here: AsposePDFIssue.zip (15.4 KB). Fill in the client_id
and client_secret
before running the script.
And here’s some example outputs of the script with the problematic requests highlighted. This proves that it is random and does not depend on the PDF content.
Got bearer token: 0.7214765000000001s
Uploaded presentation_10_slides.pdf: 1.037693s
Converted page 1: 0.9693908999999998s
**Converted page 2: 61.393300599999996s**
Converted page 3: 1.1667901s
**Converted page 4: 61.664027399999995s**
Converted page 5: 1.1803079999999824s
**Converted page 6: 62.4722635s**
Converted page 7: 1.124041200000022s
Converted page 8: 1.616950399999979s
Converted page 9: 1.4690037000000018s
Converted page 10: 1.0940741000000003s
Reached end of file
Got bearer token: 0.7325591s
Uploaded presentation_10_slides.pdf: 0.9040683999999999s
Converted page 1: 5.4563171s
Converted page 2: 0.9637957000000004s
Converted page 3: 0.9677045s
Converted page 4: 0.9525687000000005s
**Converted page 5: 61.02405370000001s**
Converted page 6: 1.4895530999999949s
Converted page 7: 0.9399642999999998s
**Converted page 8: 62.8755017s**
Converted page 9: 1.2989376000000163s
Converted page 10: 3.2490191999999922s
Reached end of file
PS: You might have to run the script multiple times. In my case, about every 5th run was smooth…
PS2: Since this seems to be related to a load-balancing issue or similar, the following information might help: we send the requests from central Europe.