From cabe2c4001dd218c0dfdf433b3a10fe140e37b4a Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Fri, 16 May 2025 11:30:13 +0200 Subject: [PATCH] fix(ins): fix 404 --- pages/instances/reference-content/choosing-instance-type.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx index 2a2484aaff..201ef27d1b 100644 --- a/pages/instances/reference-content/choosing-instance-type.mdx +++ b/pages/instances/reference-content/choosing-instance-type.mdx @@ -27,7 +27,7 @@ Instances are virtual machines: multiple Instances can run on one "real" physica * **vCPU**: A **v**irtual **C**entralized **P**rocessing **U**nit represents a part of the underlying physical CPU that is assigned to a particular Instance. - Each vCPU may be [shared or dedicated](/docs/instances/reference-content/choosing-shared-vs-dedicated-cpus/). + Each vCPU may be [shared or dedicated](/instances/reference-content/choosing-shared-vs-dedicated-cpus/). - **Shared**: A [context-switching mechanism](https://en.wikipedia.org/wiki/Context_switch) allows a physical core to be shared between multiple vCPUs for multitasking. Instances with shared vCPU can be more cost-effective for running small, non-resource-intensive applications than dedicated vCPU Instances. Our different types of shared vCPU Instances offer a variety of options to balance price and performance depending on your use case. - **Dedicated**: Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications. @@ -58,7 +58,7 @@ Use this table to help identify the right Instance range for your use case and c | **Use cases** | Discovering the Scaleway ecosystem
Hosting personal projects | Scaling your development and testing environment
Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications
Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases
Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD | | **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage or Local Storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | | **vCPU** | 1 core | From 1 to 32 cores | From 2 to 96 cores | From 2 to 64 cores | -| **Shared/Dedicated** | [Shared vCPU](/docs/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Shared vCPU](/docs/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | +| **Shared/Dedicated** | [Shared vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Shared vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | | **RAM** | 1 GiB | From 2 GiB to 128 GiB | From 8 GiB to 384 GiB | From 4 GiB to 512 GiB | | **Maximum Bandwidth** | 100 Mbit/s | From 100 Mbps to 6 Gbps | From 400 Mbps to 20 Gbps | From 400 Mbps to 12.8 Gbps |