From fa86c26b93a76eeda0efe8b5e491094ae8d72f56 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Wed, 29 Jan 2025 15:00:21 +0100 Subject: [PATCH 1/4] feat(serverless): autoscaling concept --- pages/serverless-containers/concepts.mdx | 14 ++++++++++---- pages/serverless-functions/concepts.mdx | 14 ++++++++++---- 2 files changed, 20 insertions(+), 8 deletions(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 321004a78c..23b2279ac0 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -12,6 +12,16 @@ categories: - serverless --- +## Autoscaling + +Autoscaling refers to the ability of Serverless Containers to automatically adjust the number of intances without manual intervention. +Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. + +Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/docs/serverless-containers/concepts/#max-scale), scaling policies available are: +* **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. +* **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. +* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. + ## Cold start Cold start is the time a Container takes to handle a request when it is called for the first time. @@ -182,10 +192,6 @@ A sandbox is an isolation area for your container. Serverless Containers offer t One of the advantages of Serverless Containers is that when your container is not triggered, it does not consume any resources, which enables great savings. -## Scaling - -Serverless Containers make scaling your application transparent, up to 50 instances of your container can be run at the same time. - ## Secrets Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index bd5f52c139..83cf15fb0b 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -12,6 +12,16 @@ categories: - serverless --- +## Autoscaling + +Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of intances without manual intervention. +Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. + +Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/docs/serverless-functions/concepts/#max-scale), scaling policies available are: +* **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. +* **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. +* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. + ## Build step Before deploying Serverless Functions, they have to be built. This step occurs during deployment. @@ -142,10 +152,6 @@ A sandbox is an isolation area for your function. Serverless Functions offer two One of the advantages of Serverless Functions is that when your function is not triggered, it does not consume any resources, which allows for significant savings. -## Scaling - -Serverless Functions make scaling your application transparent, up to 50 instances of your function can be run at the same time. - ## Secrets Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation. From 368bdb4feae26d6a029badc75f31de3f2b90b876 Mon Sep 17 00:00:00 2001 From: Thomas TACQUET Date: Wed, 29 Jan 2025 18:37:08 +0100 Subject: [PATCH 2/4] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- pages/serverless-containers/concepts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 23b2279ac0..0423261cd1 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -17,7 +17,7 @@ categories: Autoscaling refers to the ability of Serverless Containers to automatically adjust the number of intances without manual intervention. Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. -Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/docs/serverless-containers/concepts/#max-scale), scaling policies available are: +Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/serverless-containers/concepts/#max-scale), scaling policies available are: * **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. * **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. From 85b93c2fa4372f44296baeea63956d3d7d11916a Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Wed, 29 Jan 2025 18:37:27 +0100 Subject: [PATCH 3/4] missed review --- pages/serverless-functions/concepts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 83cf15fb0b..92059d473e 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -17,7 +17,7 @@ categories: Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of intances without manual intervention. Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. -Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/docs/serverless-functions/concepts/#max-scale), scaling policies available are: +Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/serverless-functions/concepts/#max-scale), scaling policies available are: * **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. * **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. From 17aceff6249297c978310d99f3e856979804e740 Mon Sep 17 00:00:00 2001 From: Thomas TACQUET Date: Thu, 30 Jan 2025 10:10:21 +0100 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- pages/serverless-containers/concepts.mdx | 6 +++--- pages/serverless-functions/concepts.mdx | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 0423261cd1..41b6b246c8 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -14,11 +14,11 @@ categories: ## Autoscaling -Autoscaling refers to the ability of Serverless Containers to automatically adjust the number of intances without manual intervention. +Autoscaling refers to the ability of Serverless Containers to automatically adjust the number of instances without manual intervention. Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. -Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/serverless-containers/concepts/#max-scale), scaling policies available are: -* **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. +Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/serverless-containers/concepts/#max-scale). Available scaling policies are: +* **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. * **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 92059d473e..33bd8cbbdd 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -14,11 +14,11 @@ categories: ## Autoscaling -Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of intances without manual intervention. +Autoscaling refers to the ability of Serverless Functions to automatically adjust the number of instances without manual intervention. Scaling mechanisms ensure that resources are provisioned dynamically to handle incoming requests efficiently while minimizing idle capacity and cost. -Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/serverless-functions/concepts/#max-scale), scaling policies available are: -* **Concurrent requests:** requests incoming on the ressource at the same time. Default value suitable for most use cases. +Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/serverless-functions/concepts/#max-scale). Available scaling policies are: +* **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. * **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads.