From 1392f1880fdf5df1af0cab6baf689439586189d5 Mon Sep 17 00:00:00 2001 From: Loic KHAMDY Date: Fri, 30 Oct 2026 11:27:07 +0100 Subject: [PATCH 1/3] feat(serverless): add concurrency soft limit info MTA-7622 --- .../containers-concurrency.mdx | 2 ++ .../containers-limitations.mdx | 20 ++++++++++--------- 2 files changed, 13 insertions(+), 9 deletions(-) diff --git a/pages/serverless-containers/reference-content/containers-concurrency.mdx b/pages/serverless-containers/reference-content/containers-concurrency.mdx index 111df6a90c..5c487ef3c5 100644 --- a/pages/serverless-containers/reference-content/containers-concurrency.mdx +++ b/pages/serverless-containers/reference-content/containers-concurrency.mdx @@ -15,6 +15,8 @@ Unlike Serverless Functions, which handles only one request per instance, Server A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless-containers/concepts/#vcpu), and consequently a higher cost. +Concurrency is a soft limit used as an autoscaling target, not a strict per-instance cap. A container instance can temporarily process more concurrent requests than the configured value, especially during sudden bursts of traffic or when the maximum number of instances (`maxScale`) is reached. + ``` Concurrency = 1 diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index a8d68adbdb..30e6eea3e7 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -11,14 +11,14 @@ This section contains usage limits that apply when using Serverless Containers. | Resources | Criteria | Limits | Scope | |---------------------------------------------------|------------- |------------------ |-----------------------------| -| Namespaces | Max number | 100* | Project | -| Containers | Max number | 1000* | Organization | +| Namespaces | Max number | 100\* | Project | +| Containers | Max number | 1000\* | Organization | | Total container memory\** | Max size | 600 GiB | Organization | | Custom domains | Max number | 50 | Container | | Recommended maximum uncompressed image size | Max size | 1 GB | Container | | Temporary disk size | Max size | 24 000 MiB | Container | | Invocation rate | Max number | 5000 per second | Container | -| Concurrency | Max | 80 | Container Instance | +| Concurrency\*** | Max | 80 | Container Instance | | Max Scale (simultaneous Container instances) | Max | 200 | Container | | CPU | Min/max | 70 to 6000 mvCPU | Container | | Memory | Min/Max | 128 to 12228 MB | Container | @@ -28,15 +28,17 @@ This section contains usage limits that apply when using Serverless Containers. | Secret environment variables | Max size | 65536 bytes | Secret environment variable | | Time before scale to zero | Time | 15 minutes | Instance | | Time before scale down | Time | 30 seconds | Instance | -| HTTP request duration (timeout)\*** | Min/max | 10 seconds to 60 minutes | Request | +| HTTP request duration (timeout)\**** | Min/max | 10 seconds to 60 minutes | Request | | Private Networks attached | Max | 1 | Container | | Logs | Logs | 30000 per minute | Project | -\* Lower limits may apply before account verification. Contact our Support team if you have any questions. +\* Lower limits may apply before account verification. Contact [Scaleway Support](https://console.scaleway.com/support) if you have any questions. \** Total container memory is the sum of the memory allocated to all your containers at their maximum Scale. -\*** Use [Serverless Jobs](/serverless-jobs/) for tasks up to 24h. +\*** Maximum concurrency is a soft limit used as an autoscaling target, not a strict per-instance cap. + +\**** Use [Serverless Jobs](/serverless-jobs/) for tasks up to 24h. These limits are enforced as [Organization quotas](/organizations-and-projects/organization/organization-quotas/#serverless-containers). @@ -227,11 +229,11 @@ Do not have your containers listen on these ports, as they are used by our servi ### Protocols -Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information on how to solve HTTP/1.0 issues. +Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. See the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information on how to solve HTTP/1.0 issues. ## Private Networks and Virtual Private Cloud (VPC) -Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks/) on VPC and Serverless Containers integration for more information. +See the [Serverless Containers and Private Networks integration](/serverless-containers/reference-content/containers-private-networks/) page for more information. ## Default values for CPU and memory limits @@ -275,4 +277,4 @@ leading to service disruption until a new successful deployment is made. ## Containers sandbox -Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on the limitations of sandbox environments for Serverless Containers. +See the [Containers sandbox](/serverless-containers/reference-content/containers-sandbox/) page for more information on the limitations of sandbox environments for Serverless Containers. From 26d9ece69162fca3fba2fee22f06d020fe2f39aa Mon Sep 17 00:00:00 2001 From: Loic KHAMDY Date: Fri, 30 Oct 2026 11:38:35 +0100 Subject: [PATCH 2/3] feat(serverless): add ref to concurrency page --- .../reference-content/containers-limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index 30e6eea3e7..67480819a4 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -36,7 +36,7 @@ This section contains usage limits that apply when using Serverless Containers. \** Total container memory is the sum of the memory allocated to all your containers at their maximum Scale. -\*** Maximum concurrency is a soft limit used as an autoscaling target, not a strict per-instance cap. +\*** Maximum concurrency is a soft limit used as an autoscaling target, not a strict per-instance cap. See the [Containers concurrency](/serverless-containers/reference-content/containers-concurrency/) page for more information. \**** Use [Serverless Jobs](/serverless-jobs/) for tasks up to 24h. From 50417d398c2a54b46bbfc12c429416d73d002b44 Mon Sep 17 00:00:00 2001 From: Loic-kd Date: Fri, 30 Oct 2026 18:51:37 +0100 Subject: [PATCH 3/3] Apply suggestion from @vanda-scw Co-authored-by: vanda-scw --- .../reference-content/containers-limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index 67480819a4..9dee346741 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -229,7 +229,7 @@ Do not have your containers listen on these ports, as they are used by our servi ### Protocols -Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. See the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information on how to solve HTTP/1.0 issues. +Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. See the [troubleshooting page on how to resolve HTTP/1.0 issues](/serverless-containers/troubleshooting/http1-errors/) for more information. ## Private Networks and Virtual Private Cloud (VPC)