From 42dc5d9e6211e6870d88810a4b7700a6efce4182 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Fri, 1 Aug 2025 18:28:55 +0100 Subject: [PATCH 1/9] feat: added guaranteed resources page Added new guaranteed resources page --- .../manage-resources/guaranteed-resources.md | 71 +++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 sites/upsun/src/manage-resources/guaranteed-resources.md diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md new file mode 100644 index 0000000000..9d38cf0472 --- /dev/null +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -0,0 +1,71 @@ +--- +title: Guaranteed resources +description: Learn how Guaranteed Resources on {{% vendor/name %}} provide dedicated CPU and memory allocations for consistent, high-performance workloads. +weight: -50 +--- + +For applications that need to scale beyond 8 CPUs, {{% vendor/name %}} offers Guaranteed Resources. + +Guaranteed Resources ensure that your app or service receives dedicated access to the specified amount of CPU and RAM. These resources are reserved exclusively for your container. + +All {{% vendor/name %}} containers use vCPUs (virtual CPUs). Although configuration files and dashboards use the term `CPU`, this always refers to vCPUs, not dedicated physical cores. + +vCPU performance can sometimes vary depending on factors such as: + +- Cloud provider and region +- System load from other virtual machines or services (in shared mode) + +However, using Guaranteed Resources prevents many of these variations by reserving resources just for your container. This kind of allocation provides performance close to dedicated infrastructure, ideal for: + +- Backend services +- Real-time APIs +- Load testing +- Performance-sensitive workloads + +## Enable Guaranteed Resources + +1. Open your project. +2. Click the Configure resources button from the project card or App & Services panel. +3. For each app/service: + - Select **Guaranteed** or **Shared** as the resource type. + - Choose the desired CPU and RAM combination. + - Enter the amount of Disk/Storage to allocate. +4. Click Save. Saving will redeploy your environment, which may cause temporary downtime. + +{{% note %}} + +You cannot enable Guaranteed Resources if your [container profile is set to `HIGHER_MEMORY`](/manage-resources/adjust-resources.html#advanced-container-profiles). + +{{% /note %}} + +## View your Allocated Resources + +Once Guaranteed Resources is enabled, projects will display an Allocated Resources component in the Console. This shows: + +- CPU type: Shared vs. Guaranteed +- Allocated RAM and Disk +- Live usage metrics + +{{% note %}} + +A small portion of host CPU and RAM is used by {{% vendor/name %}}’s system services. The available capacity will be slightly lower than the full allocation selected. + +{{% /note %}} + +## Pause Environments with Guaranteed Resources + +When any app or service in an environment uses Guaranteed Resources, that environment cannot be paused automatically or manually. + +This is because, with Guaranteed Resources, you're billed for the reserved CPU and memory, so allowing pause functionality would lead to potential overuse of reserved compute and incorrect billing. + +### To pause the environment again: + +1. Switch all containers using Guaranteed Resources back to shared mode. +2. Once no containers are using Guaranteed Resources, the environment can be paused as usual. + +{{% note %}} + +You can upscale to Guaranteed Resources even if the environment is currently paused. Doing so will automatically resume the environment and apply the changes. + +{{% /note %}} + From 36b7889bc649f32922662d491dc4c3c031e306a0 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Thu, 14 Aug 2025 14:55:23 +0100 Subject: [PATCH 2/9] feat: made changes suggested made suggested changes from Nicolas --- sites/upsun/src/manage-resources/_index.md | 17 ++++++++ .../manage-resources/guaranteed-resources.md | 39 ++++++++----------- 2 files changed, 34 insertions(+), 22 deletions(-) diff --git a/sites/upsun/src/manage-resources/_index.md b/sites/upsun/src/manage-resources/_index.md index e479d02ddd..74371836cf 100644 --- a/sites/upsun/src/manage-resources/_index.md +++ b/sites/upsun/src/manage-resources/_index.md @@ -27,3 +27,20 @@ Projects on Upsun run on shared hosts, which means the processing power allocate It should be noted that projects are always kept **strictly isolated** from each other. {{< /note >}} + +## Types of resources + +All {{% vendor/name %}} containers use vCPUs (virtual CPUs). Although configuration files and dashboards use the term `CPU`, this always refers to vCPUs, not dedicated physical cores. + +vCPU performance can sometimes vary depending on factors such as: + +- Cloud provider and region +- System load from other virtual machines or services (in shared mode) + + ### Types of CPU + +There are two different types of CPU {{% vendor/name %}} offers: + + - Shared: Your container is running on our Grid hosts. + - Guaranteed: Your container is running on its own dedicated host. + diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md index 9d38cf0472..905746ba7e 100644 --- a/sites/upsun/src/manage-resources/guaranteed-resources.md +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -1,28 +1,21 @@ --- -title: Guaranteed resources -description: Learn how Guaranteed Resources on {{% vendor/name %}} provide dedicated CPU and memory allocations for consistent, high-performance workloads. +title: Guaranteed CPU +description: Learn how Guaranteed CPU on {{% vendor/name %}} provide dedicated CPU and memory allocations for consistent, high-performance workloads. weight: -50 --- -For applications that need to scale beyond 8 CPUs, {{% vendor/name %}} offers Guaranteed Resources. +For applications that need to scale beyond 8 CPUs, {{% vendor/name %}} offers Guaranteed CPU. -Guaranteed Resources ensure that your app or service receives dedicated access to the specified amount of CPU and RAM. These resources are reserved exclusively for your container. +Guaranteed CPU ensure that your app or service receives dedicated access to the specified amount of CPU and RAM. These resources are reserved exclusively for your container. -All {{% vendor/name %}} containers use vCPUs (virtual CPUs). Although configuration files and dashboards use the term `CPU`, this always refers to vCPUs, not dedicated physical cores. - -vCPU performance can sometimes vary depending on factors such as: - -- Cloud provider and region -- System load from other virtual machines or services (in shared mode) - -However, using Guaranteed Resources prevents many of these variations by reserving resources just for your container. This kind of allocation provides performance close to dedicated infrastructure, ideal for: +This kind of allocation provides performance close to dedicated infrastructure, ideal for: - Backend services - Real-time APIs - Load testing - Performance-sensitive workloads -## Enable Guaranteed Resources +## Enable Guaranteed CPU 1. Open your project. 2. Click the Configure resources button from the project card or App & Services panel. @@ -34,38 +27,40 @@ However, using Guaranteed Resources prevents many of these variations by reservi {{% note %}} -You cannot enable Guaranteed Resources if your [container profile is set to `HIGHER_MEMORY`](/manage-resources/adjust-resources.html#advanced-container-profiles). +You cannot enable Guaranteed CPU if your [container profile is set to `HIGHER_MEMORY`](/manage-resources/adjust-resources.html#advanced-container-profiles). {{% /note %}} -## View your Allocated Resources +## View your Allocated CPU -Once Guaranteed Resources is enabled, projects will display an Allocated Resources component in the Console. This shows: +All projects display an Allocated Resources component in the Console. This shows: - CPU type: Shared vs. Guaranteed - Allocated RAM and Disk - Live usage metrics +It will also show whether you have Guaranteed CPU is enabled or not. + {{% note %}} A small portion of host CPU and RAM is used by {{% vendor/name %}}’s system services. The available capacity will be slightly lower than the full allocation selected. {{% /note %}} -## Pause Environments with Guaranteed Resources +## Pause Environments with Guaranteed CPU -When any app or service in an environment uses Guaranteed Resources, that environment cannot be paused automatically or manually. +When any app or service in an environment uses Guaranteed CPU, that environment cannot be paused automatically or manually. -This is because, with Guaranteed Resources, you're billed for the reserved CPU and memory, so allowing pause functionality would lead to potential overuse of reserved compute and incorrect billing. +This is because, with Guaranteed CPU, you're billed for the reserved CPU and memory, so allowing pause functionality would lead to potential overuse of reserved compute and incorrect billing. ### To pause the environment again: -1. Switch all containers using Guaranteed Resources back to shared mode. -2. Once no containers are using Guaranteed Resources, the environment can be paused as usual. +1. Switch all containers using Guaranteed CPU back to shared mode. +2. Once no containers are using Guaranteed CPU, the environment can be paused as usual. {{% note %}} -You can upscale to Guaranteed Resources even if the environment is currently paused. Doing so will automatically resume the environment and apply the changes. +You can upscale to Guaranteed CPU even if the environment is currently paused. Doing so will automatically resume the environment and apply the changes. {{% /note %}} From ee8c23c5f176eb5e0c5360235fb02dcef2f40bbc Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Thu, 25 Sep 2025 14:55:46 +0100 Subject: [PATCH 3/9] feat: added new page and changes Made suggested changes and added new page for index --- sites/upsun/src/manage-resources/_index.md | 28 +------- .../manage-resources/guaranteed-resources.md | 28 +++----- .../manage-resources/how-resources-work.md | 67 +++++++++++++++++++ 3 files changed, 78 insertions(+), 45 deletions(-) create mode 100644 sites/upsun/src/manage-resources/how-resources-work.md diff --git a/sites/upsun/src/manage-resources/_index.md b/sites/upsun/src/manage-resources/_index.md index 74371836cf..629c227e41 100644 --- a/sites/upsun/src/manage-resources/_index.md +++ b/sites/upsun/src/manage-resources/_index.md @@ -13,34 +13,10 @@ keywords: - "scaling" --- -{{% vendor/name %}} allows you to configure resources (CPU, RAM, and disk) per environment for each of your apps and services. -You can also add instances for each of your apps depending on your needs. +{{% note theme="note" title="Understand your resource options"%}} -For information on costs related to resource usage, see the [{{% vendor/name %}} pricing page](https://upsun.com/pricing/). - -## How resources work on Upsun - -Projects on Upsun run on shared hosts, which means the processing power allocated to your containers can be dependent on resources other customers are using on the same hosts. Our orchestration layer works to ensure stable access to resources when possible, however some variability should be expected due to the shared infrastructure of our regions. - -{{< note theme="info" >}} - - It should be noted that projects are always kept **strictly isolated** from each other. +To understand how resources work on {{% vendor/name %}} and learn more about your options, visit the [How resources work](/manage-resources/how-resources-work.html) page. {{< /note >}} -## Types of resources - -All {{% vendor/name %}} containers use vCPUs (virtual CPUs). Although configuration files and dashboards use the term `CPU`, this always refers to vCPUs, not dedicated physical cores. - -vCPU performance can sometimes vary depending on factors such as: - -- Cloud provider and region -- System load from other virtual machines or services (in shared mode) - - ### Types of CPU - -There are two different types of CPU {{% vendor/name %}} offers: - - - Shared: Your container is running on our Grid hosts. - - Guaranteed: Your container is running on its own dedicated host. diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md index 905746ba7e..15e77b203e 100644 --- a/sites/upsun/src/manage-resources/guaranteed-resources.md +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -1,10 +1,10 @@ --- -title: Guaranteed CPU +title: Guaranteed resources description: Learn how Guaranteed CPU on {{% vendor/name %}} provide dedicated CPU and memory allocations for consistent, high-performance workloads. -weight: -50 +weight: -350 --- -For applications that need to scale beyond 8 CPUs, {{% vendor/name %}} offers Guaranteed CPU. +For applications or services that need to scale to large resources and have performance guarantees, {{% vendor/name %}} offers Guaranteed resources (Guaranteed CPU). Guaranteed CPU ensure that your app or service receives dedicated access to the specified amount of CPU and RAM. These resources are reserved exclusively for your container. @@ -15,6 +15,12 @@ This kind of allocation provides performance close to dedicated infrastructure, - Load testing - Performance-sensitive workloads +{{% note theme="warning" title="Region availability"%}} + +Guaranteed CPU is **not supported on OVHcloud regions**, and some sizes **may not be available for [all regions](/development/regions.html).** + +{{% /note %}} + ## Enable Guaranteed CPU 1. Open your project. @@ -31,22 +37,6 @@ You cannot enable Guaranteed CPU if your [container profile is set to `HIGHER_ME {{% /note %}} -## View your Allocated CPU - -All projects display an Allocated Resources component in the Console. This shows: - -- CPU type: Shared vs. Guaranteed -- Allocated RAM and Disk -- Live usage metrics - -It will also show whether you have Guaranteed CPU is enabled or not. - -{{% note %}} - -A small portion of host CPU and RAM is used by {{% vendor/name %}}’s system services. The available capacity will be slightly lower than the full allocation selected. - -{{% /note %}} - ## Pause Environments with Guaranteed CPU When any app or service in an environment uses Guaranteed CPU, that environment cannot be paused automatically or manually. diff --git a/sites/upsun/src/manage-resources/how-resources-work.md b/sites/upsun/src/manage-resources/how-resources-work.md new file mode 100644 index 0000000000..5af50ef2d8 --- /dev/null +++ b/sites/upsun/src/manage-resources/how-resources-work.md @@ -0,0 +1,67 @@ +--- +title: How resources work on {{% vendor/name %}} +description: Configure resources per environment for each of your apps and services. +weight: -400 +keywords: + - "resources" + - "flexible resources" + - "CPU" + - "RAM" + - "disk storage" +--- + +On **{{% vendor/name %}} Flex**, you have granular control over your application's resources. Instead of choosing from pre-defined plans, you can configure resources (CPU, RAM, and disk) per environment for each of your apps and services. You can also add instances for each of your apps depending on your needs. + +Understanding how allocates these resources is key to building a performant, stable, and cost-effective architecture for your project. + +For information on costs related to resource usage, see the [{{% vendor/name %}} pricing page](https://upsun.com/pricing/). + +## CPUs vs. vCPUs + +Throughout our product and documentation, when we refer to **CPU**, we are describing **vCPUs (virtual CPUs)**. A vCPU is a virtualized representation of a physical CPU core. This is the standard for cloud computing, as it allows a physical server's resources to be securely divided among multiple applications. + +vCPU performance can sometimes vary depending on factors such as: + +- Cloud provider and [region](/developemnt/regions.html) +- System load from other containers on a shared host (in shared mode) + +## CPU: Shared vs. Guaranteed + +CPU resources can be allocated in two distinct ways. This choice allows you to precisely balance cost with performance needs for each individual container in your project. + +### Shared CPU (Default) + +By default, projects on {{% vendor/name %}} Flex run on **shared hosts**, which means the processing power allocated to your containers can be dependent on resources other customers are using on the same hosts. Our orchestration layer works to ensure stable access to resources when possible, however some variability should be expected due to the shared infrastructure of our regions. + +{{< note theme="info" >}} + + It should be noted that projects are always kept **strictly isolated** from each other. + +{{< /note >}} + +**Best for:** +- Containers in development/staging environments +- Production containers with low-to-moderate traffic + +**Consideration:** +- Performance can be variable due to the "noisy neighbour" effect inherent in shared infrastructure. + +### Guaranteed CPU + +With [Guaranteed CPU](/manage-resources/guaranteed-resources), your container is placed on a dedicated host, and the host's CPU resources are reserved exclusively for your container's use. This provides the highest level of CPU performance and predictability by eliminating any "noisy neighbour" effect. + +**Best for:** +- High-traffic production application containers +- Resource-intensive services (e.g. database, search engine) +- Any container requiring large resource allocations with consistent and predictable performance + +**Consideration:** +- This option has a higher cost due to its dedicated nature. +- A small portion of host CPU and RAM is used by {{% vendor/name %}}’s system services. The available capacity will be slightly lower than the full allocation selected. + +## Memory (RAM) + +The memory (RAM) you configure for a container is **always guaranteed**. + +This means the full amount of RAM you define is exclusively available to that container and is never shared. This guarantees predictable memory performance and prevents issues caused by other applications on the same host, regardless of your chosen CPU type. + From c7d8edb61277adf3e8c74513a40c37e3573687fc Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Fri, 26 Sep 2025 14:07:40 +0100 Subject: [PATCH 4/9] feat: made changes Rearranged structure and merged best for points --- sites/upsun/src/manage-resources/_index.md | 2 +- sites/upsun/src/manage-resources/autoscaling.md | 2 +- sites/upsun/src/manage-resources/build-resources.md | 2 +- sites/upsun/src/manage-resources/guaranteed-resources.md | 8 +++++--- 4 files changed, 8 insertions(+), 6 deletions(-) diff --git a/sites/upsun/src/manage-resources/_index.md b/sites/upsun/src/manage-resources/_index.md index 629c227e41..fb3bcc1c32 100644 --- a/sites/upsun/src/manage-resources/_index.md +++ b/sites/upsun/src/manage-resources/_index.md @@ -15,7 +15,7 @@ keywords: {{% note theme="note" title="Understand your resource options"%}} -To understand how resources work on {{% vendor/name %}} and learn more about your options, visit the [How resources work](/manage-resources/how-resources-work.html) page. +To understand how resources work on {{% vendor/name %}} and learn more about your options, visit the [how resources work](/manage-resources/how-resources-work.html) page. {{< /note >}} diff --git a/sites/upsun/src/manage-resources/autoscaling.md b/sites/upsun/src/manage-resources/autoscaling.md index 1ea98863d1..881a14f74a 100644 --- a/sites/upsun/src/manage-resources/autoscaling.md +++ b/sites/upsun/src/manage-resources/autoscaling.md @@ -1,7 +1,7 @@ --- title: Autoscaling description: Learn how autoscaling dynamically adjusts app instances based on CPU usage to keep apps responsive under load while optimizing costs. -weight: -400 +weight: -100 keywords: - "resources" - "CPU" diff --git a/sites/upsun/src/manage-resources/build-resources.md b/sites/upsun/src/manage-resources/build-resources.md index ed20802962..a53d7aa16f 100644 --- a/sites/upsun/src/manage-resources/build-resources.md +++ b/sites/upsun/src/manage-resources/build-resources.md @@ -1,7 +1,7 @@ --- title: Project build resources description: Configure project build resources on {{% vendor/name %}}. -weight: -50 +weight: -30 --- When you push changes through Git, your applications are first built, then deployed. diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md index 15e77b203e..b4f7065d53 100644 --- a/sites/upsun/src/manage-resources/guaranteed-resources.md +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -1,7 +1,7 @@ --- title: Guaranteed resources description: Learn how Guaranteed CPU on {{% vendor/name %}} provide dedicated CPU and memory allocations for consistent, high-performance workloads. -weight: -350 +weight: -50 --- For applications or services that need to scale to large resources and have performance guarantees, {{% vendor/name %}} offers Guaranteed resources (Guaranteed CPU). @@ -13,7 +13,9 @@ This kind of allocation provides performance close to dedicated infrastructure, - Backend services - Real-time APIs - Load testing -- Performance-sensitive workloads +- High-traffic production application containers +- Resource-intensive services (e.g. database, search engine) +- Any container requiring large resource allocations with consistent and predictable performance {{% note theme="warning" title="Region availability"%}} @@ -37,7 +39,7 @@ You cannot enable Guaranteed CPU if your [container profile is set to `HIGHER_ME {{% /note %}} -## Pause Environments with Guaranteed CPU +## Pause environments with Guaranteed CPU When any app or service in an environment uses Guaranteed CPU, that environment cannot be paused automatically or manually. From a20471dac3df321b4a93384d13cf3023ef203037 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Fri, 26 Sep 2025 14:14:33 +0100 Subject: [PATCH 5/9] feat: added description added correct description --- sites/upsun/src/manage-resources/how-resources-work.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sites/upsun/src/manage-resources/how-resources-work.md b/sites/upsun/src/manage-resources/how-resources-work.md index 5af50ef2d8..e12dabc739 100644 --- a/sites/upsun/src/manage-resources/how-resources-work.md +++ b/sites/upsun/src/manage-resources/how-resources-work.md @@ -1,6 +1,6 @@ --- title: How resources work on {{% vendor/name %}} -description: Configure resources per environment for each of your apps and services. +description: Understand how resources work on {{% vendor/name %}} Flex. Learn the differences between shared and guaranteed CPU, how RAM is allocated, and how to configure scalable resources for your apps. weight: -400 keywords: - "resources" @@ -12,7 +12,7 @@ keywords: On **{{% vendor/name %}} Flex**, you have granular control over your application's resources. Instead of choosing from pre-defined plans, you can configure resources (CPU, RAM, and disk) per environment for each of your apps and services. You can also add instances for each of your apps depending on your needs. -Understanding how allocates these resources is key to building a performant, stable, and cost-effective architecture for your project. +Understanding how {{% vendor/name %}} allocates these resources is key to building a performant, stable, and cost-effective architecture for your project. For information on costs related to resource usage, see the [{{% vendor/name %}} pricing page](https://upsun.com/pricing/). From 5eab342c1074ff5b7d40af7b8199803d43522440 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Fri, 26 Sep 2025 14:18:02 +0100 Subject: [PATCH 6/9] feat: adjusted enable steps Adjusted steps in section. --- sites/upsun/src/manage-resources/guaranteed-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md index b4f7065d53..ca0c9fa27f 100644 --- a/sites/upsun/src/manage-resources/guaranteed-resources.md +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -26,7 +26,7 @@ Guaranteed CPU is **not supported on OVHcloud regions**, and some sizes **may no ## Enable Guaranteed CPU 1. Open your project. -2. Click the Configure resources button from the project card or App & Services panel. +2. Click the Configure resources button from the Allocated resources block. 3. For each app/service: - Select **Guaranteed** or **Shared** as the resource type. - Choose the desired CPU and RAM combination. From e584da02b903bf02a4474e5a6ae71ce8009e7fd0 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Mon, 29 Sep 2025 14:02:36 +0100 Subject: [PATCH 7/9] feat: corrected typo corrected typo in url --- sites/upsun/src/manage-resources/how-resources-work.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/upsun/src/manage-resources/how-resources-work.md b/sites/upsun/src/manage-resources/how-resources-work.md index e12dabc739..02f5b89ebe 100644 --- a/sites/upsun/src/manage-resources/how-resources-work.md +++ b/sites/upsun/src/manage-resources/how-resources-work.md @@ -22,7 +22,7 @@ Throughout our product and documentation, when we refer to **CPU**, we are descr vCPU performance can sometimes vary depending on factors such as: -- Cloud provider and [region](/developemnt/regions.html) +- Cloud provider and [region](/development/regions.html) - System load from other containers on a shared host (in shared mode) ## CPU: Shared vs. Guaranteed From c17418bdcbeb0a57b715bd4520cb250135626f9e Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Mon, 29 Sep 2025 14:08:32 +0100 Subject: [PATCH 8/9] feat: changed syntax Changed syntax after vale failure --- sites/upsun/src/manage-resources/how-resources-work.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sites/upsun/src/manage-resources/how-resources-work.md b/sites/upsun/src/manage-resources/how-resources-work.md index 02f5b89ebe..3789dc50b8 100644 --- a/sites/upsun/src/manage-resources/how-resources-work.md +++ b/sites/upsun/src/manage-resources/how-resources-work.md @@ -12,13 +12,13 @@ keywords: On **{{% vendor/name %}} Flex**, you have granular control over your application's resources. Instead of choosing from pre-defined plans, you can configure resources (CPU, RAM, and disk) per environment for each of your apps and services. You can also add instances for each of your apps depending on your needs. -Understanding how {{% vendor/name %}} allocates these resources is key to building a performant, stable, and cost-effective architecture for your project. +Understanding how {{% vendor/name %}} allocates these resources is key to building stable and cost-effective architecture for your project. For information on costs related to resource usage, see the [{{% vendor/name %}} pricing page](https://upsun.com/pricing/). ## CPUs vs. vCPUs -Throughout our product and documentation, when we refer to **CPU**, we are describing **vCPUs (virtual CPUs)**. A vCPU is a virtualized representation of a physical CPU core. This is the standard for cloud computing, as it allows a physical server's resources to be securely divided among multiple applications. +Throughout our product and documentation, when we refer to **CPU**, we are describing **vCPUs (virtual CPUs)**. A vCPU is a virtual representation of a physical CPU core. This is the standard for cloud computing, as it allows a physical server's resources to be securely divided among multiple applications. vCPU performance can sometimes vary depending on factors such as: From 2049b4f33c6959cc5134c6b73f98f6fbeb6899d8 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Mon, 29 Sep 2025 19:47:44 +0100 Subject: [PATCH 9/9] feat: changed syntax changed redeploy to rebuild to accurately illustrate the cause of temporary downtime --- sites/upsun/src/manage-resources/guaranteed-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/upsun/src/manage-resources/guaranteed-resources.md b/sites/upsun/src/manage-resources/guaranteed-resources.md index ca0c9fa27f..9e5a38a6aa 100644 --- a/sites/upsun/src/manage-resources/guaranteed-resources.md +++ b/sites/upsun/src/manage-resources/guaranteed-resources.md @@ -31,7 +31,7 @@ Guaranteed CPU is **not supported on OVHcloud regions**, and some sizes **may no - Select **Guaranteed** or **Shared** as the resource type. - Choose the desired CPU and RAM combination. - Enter the amount of Disk/Storage to allocate. -4. Click Save. Saving will redeploy your environment, which may cause temporary downtime. +4. Click Save. Saving will rebuild your environment, which may cause temporary downtime. {{% note %}}