Concurrency Limit for Processing Recordings During High Load

We’ve implemented a new concurrency limit mechanism that activates ONLY when a processing server hits a certain threshold considered a high load.

It works in the following way #

The concurrency limit means only a specified number of recordings may be processed at a time per account by our processing servers. Each account has a concurrency limit value based on the account type:

• Trial accounts: 1 maximum number of concurrent recordings processed during load
• Standard/Creator accounts: 2 maximum number of concurrent recordings processed during load
• PRO accounts: 4 maximum number of concurrent recordings processed during load

The above limits will be enforced when more than half of the available processing workers on the server are in use at any given moment. Otherwise, the per-account limits are ignored, and accounts can ‘burst’ and use more workers than their limit allows for recording processing.

Things to note #

• The concurrency limits are individually enforced for each recording region. This means, for example, that you may go over the limit on the US1 region but still be under the limit on US2.
• Any recording that will be denied being processed because of going over the limit will be retried by our retry mechanism.