Skip to content

Commit 396be92

Browse files
authored
Update limits.mdx (#24747)
Add note on how fill rates work for our limits.
1 parent abfe3e5 commit 396be92

File tree

1 file changed

+8
-5
lines changed
  • src/content/docs/browser-rendering/platform

1 file changed

+8
-5
lines changed

src/content/docs/browser-rendering/platform/limits.mdx

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,9 @@ To increase this limit, you will need to [upgrade to a Workers Paid plan](/worke
2121
| Concurrent browsers per account (Workers Bindings only) | 3 per account |
2222
| New browser instances per minute (Workers Bindings only) | 3 per minute |
2323
| Browser timeout | 60 seconds |
24-
| Total requests per min (REST API only) | 6 per minute |
24+
| Total requests per min (REST API only) | 6 per minute [^1] |
25+
26+
[^1]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 60 requests per minute translates to **1 request per second**. This means you cannot send all 60 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate.
2527

2628
:::note[Note on browser timeout]
2729
By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
@@ -35,12 +37,13 @@ The limits for Browser Rendering will continue to be raised over time. In the me
3537

3638
| Feature | Limit |
3739
| -------------------------------------- | ------------------- |
38-
| Concurrent browsers per account (Workers Bindings only) | 10 per account [^1] |
39-
| New browser instances per minute (Workers Bindings only) | 10 per minute [^1] |
40+
| Concurrent browsers per account (Workers Bindings only) | 10 per account [^2] |
41+
| New browser instances per minute (Workers Bindings only) | 10 per minute [^2] |
4042
| Browser timeout | 60 seconds |
41-
| Total requests per min (REST API only) | 60 per minute [^1] |
43+
| Total requests per min (REST API only) | 60 per minute [^1] [^2] |
4244

43-
[^1]: Contact our team to request increases to this limit.
45+
[^1]: Rate limits are enforced with a fixed **per-second fill rate**. For example, a limit of 60 requests per minute translates to **1 request per second**. This means you cannot send all 60 requests at once; the API expects them to be spread evenly over the minute. If your account has a custom higher limit, it will also be enforced as a per-second rate.
46+
[^2]: Contact our team to request increases to this limit.
4447

4548
:::note[Note on browser timeout]
4649
By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the [`keep_alive` option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.

0 commit comments

Comments
 (0)