Skip to main content
Legacy Parse uses a different concurrency model. See Concurrency Throttle (Legacy).

​
Page Concurrency

Page concurrency is the number of pages of your r-1 and r-1 mini jobs that Reducto processes at the same time for your account. Pages above the limit wait in a queue, and Reducto processes them as soon as capacity is available.

​
r-1

​
r-1 mini

Enterprise accounts can get custom caps. Contact sales to discuss. US is the default region. The EU column applies to requests that you send to the EU region. All values are in pages of your jobs in progress at the same time.

​
Limit Mechanisms

​
How Page Concurrency Works

  • Work above the cap waits. Reducto queues the extra work and runs it when other work completes. You see added latency, not a 429.
  • Higher limits. If your tail latency increases at high volume, the cause is work that waits in the queue. Contact sales for higher limits.
  • The cap is fixed. The cap does not grow with your traffic.
  • Each model has its own cap. r-1 pages do not count against the r-1 mini cap, and r-1 mini pages do not count against the r-1 cap.
  • Each region has its own cap. Pages in the US region do not count against your EU cap.

​
Edge Rate Limits

Edge rate limits apply to every request at the ingress and protect against accidental floods. They cap requests per second, not concurrent work. Requests above the cap return 429 immediately. The SDKs retry 429 responses with exponential backoff automatically.

​
Per API Key

If you hit [CODE 2000], you’re polling job status faster than necessary. Switch to webhooks so Reducto pushes results when ready.