How performant is the "jobs" queue?Respondida
I started using the job_statuses endpoint of the Zendesk Support API because I had to mass delete old tickets. The Deletion (with a little shell script) works well, but I am missing information of how powerful the queue processing is to ensure a stable performance.
What is the recommended way to set up the timing of "deleting 630000 tickets" (i. e. 6300 API calls)? Can I radically fill the queue and the system will handle it?
To stay on the safe side I decided to only do 2 calls per minute, later increased to 5 calls when I found out that one job needs "about 10 seconds" to complete. It would be very helpful to just see a start time or duration to exactly monitor the progress...
There is a limit of 30 jobs for those kinds of endpoints, so I would say that the best way to go about it would be to send those calls 30 by 30.
If you end up reaching the limit, you should receive an error "TooManyJobs" returning the ids of the ongoing jobs that filled the queue, so you can simply wait a bit and retry those.
There is no start time, however the Job Statuses endpoint should return the "progress" attribute showing how many items have been processed by the job. It should give you some information about the progress if needed.
Hope this help.
Publicação fechada para comentários.