Skip to content

Commit 0d8a917

Browse files
Oxyjunmarciocloudflare
Oxyjun
and
marciocloudflare
authored
[DO] Relocating the limit increase box away from the footnotes for clarity. (#17575)
* Relocating the limit increase box away from the footnotes for clarity. * Using new footnote components instead of superscripts. * Update src/content/docs/durable-objects/platform/limits.mdx Co-authored-by: marciocloudflare <[email protected]> --------- Co-authored-by: marciocloudflare <[email protected]>
1 parent b841ca5 commit 0d8a917

File tree

1 file changed

+11
-11
lines changed
  • src/content/docs/durable-objects/platform

1 file changed

+11
-11
lines changed

‎src/content/docs/durable-objects/platform/limits.mdx‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -10,27 +10,25 @@ import { Render } from "~/components";
1010

1111
Durable Objects are only available on the [Workers Paid plan](/workers/platform/pricing/#workers). Durable Objects limits are the same as [Workers Limits](/workers/platform/limits/), as well as the following limits that are specific to Durable Objects:
1212

13-
| Feature | Limit for class with key-value storage backend | Limit for class with SQite storage backend <sup>1</sup> |
14-
| --------------------------------- | ---------------------------------------------------------------- | --------------------------------------------- |
13+
| Feature | Limit for class with key-value storage backend | Limit for class with SQite storage backend [^1] |
14+
| --------------------------------- | ---------------------------------------------------------------- | ----------------------------------------------- |
1515
| Number of Objects | Unlimited (within an account or of a given class) | Unlimited (within an account or of a given class) |
1616
| Maximum Durable Object namespaces | 500 (identical to the [script limit](/workers/platform/limits/)) | 500 (identical to the [script limit](/workers/platform/limits/)) |
17-
| Storage per account | 50 GB (can be raised by contacting Cloudflare) <sup>2</sup> | 50 GB (can be raised by contacting Cloudflare) <sup>2</sup> |
17+
| Storage per account | 50 GB (can be raised by contacting Cloudflare) [^2] | 50 GB (can be raised by contacting Cloudflare) [^2] |
1818
| Storage per class | Unlimited | Unlimited |
19-
| Storage per Durable Object | Unlimited | 1 GB <sup>4</sup> |
19+
| Storage per Durable Object | Unlimited | 1 GB [^3] |
2020
| Key size | 2 KiB (2048 bytes) | Key and value combined cannot exceed 2 MB |
2121
| Value size | 128 KiB (131072 bytes) | Key and value combined cannot exceed 2 MB |
2222
| WebSocket message size | 1 MiB (only for received messages) | 1 MiB (only for received messages) |
23-
| CPU per request | 30s (including WebSocket messages) <sup>3</sup> | 30s (including WebSocket messages) <sup>3</sup> |
23+
| CPU per request | 30s (including WebSocket messages) [^4] | 30s (including WebSocket messages) [^4] |
2424

25-
<sup>1</sup> The new beta version of Durable Objects is available where each Durable Object has a private, embedded SQLite database. When creating a Durabe Object class, users can [opt-in to using SQL storage](/durable-objects/reference/durable-objects-migrations/#enable-sql-storage-on-create-durable-object-class-migration).
25+
[^1]: The new beta version of Durable Objects is available where each Durable Object has a private, embedded SQLite database. When creating a Durable Object class, users can [opt-in to using SQL storage](/durable-objects/reference/durable-objects-migrations/#enable-sql-storage-on-create-durable-object-class-migration).
2626

27-
<sup>2</sup> Durable Objects both bills and measures storage based on a gigabyte <br/> (1 GB = 1,000,000,000 bytes) and not a gibibyte (GiB). <br/>
27+
[^2]: Durable Objects both bills and measures storage based on a gigabyte <br/> (1 GB = 1,000,000,000 bytes) and not a gibibyte (GiB). <br/>
2828

29-
<sup>3</sup> Each incoming HTTP request or WebSocket *message* resets the remaining available CPU time to 30 seconds. This allows the Durable Object to consume up to 30 seconds of compute after each incoming network request, with each new network request resetting the timer. If you consume more than 30 seconds of compute between incoming network requests, there is a heightened chance that the individual Durable Object is evicted and reset.
29+
[^3]: Will be raised to 10 GB for general availability.
3030

31-
<sup>4</sup> Will be raised to 10GB for general availability.
32-
33-
<Render file="limits_increase" product="workers" />
31+
[^4]: Each incoming HTTP request or WebSocket *message* resets the remaining available CPU time to 30 seconds. This allows the Durable Object to consume up to 30 seconds of compute after each incoming network request, with each new network request resetting the timer. If you consume more than 30 seconds of compute between incoming network requests, there is a heightened chance that the individual Durable Object is evicted and reset.
3432

3533
For Durable Object classes with [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) these SQL limits apply:
3634

@@ -44,6 +42,8 @@ For Durable Object classes with [SQLite storage backend](/durable-objects/best-p
4442
| Maximum arguments per SQL function | 32 |
4543
| Maximum characters (bytes) in a `LIKE` or `GLOB` pattern | 50 bytes |
4644

45+
<Render file="limits_increase" product="workers" />
46+
4747
## How much work can a single Durable Object do?
4848

4949
Durable Objects can scale horizontally across many Durable Objects. Each individual Object is inherently single-threaded.

0 commit comments

Comments
 (0)