From 7117eb8fee7648ac853b95be874fceeff87b31f6 Mon Sep 17 00:00:00 2001 From: Jun Lee Date: Wed, 16 Oct 2024 16:46:53 +0100 Subject: [PATCH] Relocating the limit increase box away from the footnotes for clarity. --- src/content/docs/durable-objects/platform/limits.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx index d147e6b2d69689..f1946c4da9b802 100644 --- a/src/content/docs/durable-objects/platform/limits.mdx +++ b/src/content/docs/durable-objects/platform/limits.mdx @@ -30,8 +30,6 @@ Durable Objects are only available on the [Workers Paid plan](/workers/platform/ 4 Will be raised to 10GB for general availability. - - For Durable Object classes with [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) these SQL limits apply: | SQL | Limit | @@ -44,6 +42,8 @@ For Durable Object classes with [SQLite storage backend](/durable-objects/best-p | Maximum arguments per SQL function | 32 | | Maximum characters (bytes) in a `LIKE` or `GLOB` pattern | 50 bytes | + + ## How much work can a single Durable Object do? Durable Objects can scale horizontally across many Durable Objects. Each individual Object is inherently single-threaded.