Legacy Dev Forum Posts

beliczazsolt | 2022-05-30 08:17:29 UTC | #1

Hi, I see there are a couple of questions around the slowness when downloading recordings in bulk but I didnt see clear answers to the followings:

1. We can use multiple threads to run multiple jobs in parallel (max 100 entry in each job). What is the maximum number of jobs which can be in progress at any time with a single OAuth2 client? is it still ok to run 10 jobs concurrently?
2. What is the maximum time a job can run? I can see in my tests that it varied from 5 to 15 minutes but is there a limit (max value)? It is hard to plan scheduled running of the application if we dont know the maximum time a job will be completed for sure.

thanks, Zsolt

John_Carnell | 2022-06-01 20:01:27 UTC | #2

Hi Zsolt,

Let me try and answer this.

1. You can run multiple threads in parallel, but remember you can only process 300 requests per minute per OAuth Client before you started getting rate limited. You can have up to a maximum of 10 unique OAuth2 tokens running at any 1 given so the absolute maximum throughput rate for your account is 3000 requests per minute if you use all 10 of your OAuth clients tokens. If you have no other integrations running at the same time this job is running that should be fine.

Note: Rather than having 10 tokens, you can request our Care team up the limit of tokens to 3000 for a single token. You will still only get a maximum of 3000 requests per minute throughput, but you will not need to juggle multiple tokens to get the 3000 requests per minute limit.

2. Usually we document any specific API rate limits here. I do not see any limits defined here for the maximum amount of time for jobs to run. We work hard to get these limits documented, but not everything has been documented yet. I am going to drop a line to the development team and see if they have any additional thoughts.

I hope that helps.

Thanks, John Carnell Manager, Developer Engagement

beliczazsolt | 2022-06-01 20:07:43 UTC | #3

Thanks John, it helps. I didn't know that it is possible to increase the limit of a token . I am going to create a simple app and run some tests to see the average, minimum and maximum values of the jobs. I will also see the good old way to download recordings one by one (instead of a bulk job), it doesn't sound overly complicated and it may do the job for us if we don't have a very big list to process. Let me know if you get any confirmation back from your developer team, it would still be good if there is an upper limit for the completion of the jobs.

Zsolt

John_Carnell | 2022-06-01 20:17:03 UTC | #4

Hi Zsolt,

Cool. Just keep in mind that you are not upping the rate limit for all your calls. You are basically saying that rather than using 10 tokens * 300 API calls you are asking for 1 token * 3000 API calls. It's important to keep this in mind because if you have other integrations running at the time you are running this job, you can inadvertently starve your other integrations and cause them to get 429s.

Thanks, John

system | 2022-07-02 20:17:57 UTC | #5

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

This post was migrated from the old Developer Forum.

ref: 14931