From a620d673ae237b4e25947485f08443c5acc5a23b Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Wed, 8 Apr 2026 11:50:46 +0200 Subject: [PATCH 1/7] docs(file): update --- .../reference-content/limitations.mdx | 56 +++++++++++++++---- 1 file changed, 45 insertions(+), 11 deletions(-) diff --git a/pages/file-storage/reference-content/limitations.mdx b/pages/file-storage/reference-content/limitations.mdx index c893bf8907..94764685e6 100644 --- a/pages/file-storage/reference-content/limitations.mdx +++ b/pages/file-storage/reference-content/limitations.mdx @@ -1,15 +1,56 @@ --- -title: File Storage limitations -description: This page lists the limitations of Scaleway File Storage. +title: File Storage and Instances selection guidelines +description: This page explains how to provision the right file system for your Instance based on your use case. tags: limits limitations scaleway file storage file system dates: validation: 2026-01-27 posted: 2026-01-27 --- -## Maximum number of file systems attached -To ensure optimum performance, the number of file systems you can attach to an Instance is limited based on the Instance's configuration, as shown in the table below. +Overview +Scaleway File Storage performance (IOPS and Throughput) scales linearly with your provisioned capacity. To ensure your compute resources don't become a bottleneck, it is essential to pair your storage volume with an Instance type that matches its performance profile and supports the required number of mount points. +1. The Performance-to-Capacity Correlation +Our File Storage architecture follows a "pay-as-you-grow" performance model: +IOPS: Increase as you provision more GBs, up to the instance’s network limit. +Throughput: Higher provisioning unlocks greater bandwidth for data-intensive read/write operations. + +## Use cases + +To optimize your ROI and avoid "throttling" your storage at the instance level, follow these guidelines based on your provisioned capacity. + +### Light web applications and development environments + +Best For: Small web servers, dev/test environments, and low-traffic repositories. + +- Provisioning Range: 25 GB to 100 GB +- Recommended Instance: POP2-2C (or any 2 vCPU General Purpose instance), BASIC3-X, BASIC2 + +Note: Ideal for 1 or 2 mount points to maintain a stable network baseline. + +### Business applications and production environments + +Provisioning Range: 100 GB to 500 GB +Recommended Instances: POP2-4C / STANDARD3-X4C +Best For: Medium-sized CMS Web applications, application servers, and corporate media file sharing, CI/CD runner cache sharing +Advantage: These instances provide the necessary network overhead to handle the increased throughput of mid-range storage. + +### High-Performance and data intensive workloads + +Provisioning Range: Above 1 TB +Recommended Instances: All GPU Instances or CPU 8C, 16C and above. +Best For: AI/ML Fine-tuning and Inference, Video Encoding, Throughput intensive applications. +Why: At 1 TB+, File Storage delivers significant throughput. Only high-core count or GPU instances have the network "pipe" required to ingest this level of data without latency. + +## File system attachements per Instance type + +To ensure optimum performance, the number of file systems you can attach to an Instance is limited based on the Instance's configuration. + +You can find the maximum number of file systems you can attach to a Scaleway Instance using the following [Scaleway CLI](/scaleway-cli/quickstart/) command. Do not forget to replace the value of the `zone` parameter with the desired Availability Zone: + +```bash +scw instance server-type list zone=fr-par-2 +``` | NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS | |------------------|-----|-----|---------|--------|------------------| @@ -41,10 +82,3 @@ To ensure optimum performance, the number of file systems you can attach to an I | POP2-64C-256G | 64 | 0 | 256 GiB | x86_64 | 16 | | POP2-HM-48C-384G | 48 | 0 | 384 GiB | x86_64 | 12 | | POP2-HM-64C-512G | 64 | 0 | 512 GiB | x86_64 | 16 | - - -You can find the maximum number of file systems you can attach to a Scaleway Instance using the following [Scaleway CLI](/scaleway-cli/quickstart/) command: -```bash -scw instance server-type list -``` - \ No newline at end of file From cf7c395845d34b87a13818abf7cc4163490005d8 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Wed, 8 Apr 2026 14:30:18 +0200 Subject: [PATCH 2/7] docs(file): update --- .../reference-content/limitations.mdx | 117 ++++++++++++------ 1 file changed, 76 insertions(+), 41 deletions(-) diff --git a/pages/file-storage/reference-content/limitations.mdx b/pages/file-storage/reference-content/limitations.mdx index 94764685e6..7c110ec64c 100644 --- a/pages/file-storage/reference-content/limitations.mdx +++ b/pages/file-storage/reference-content/limitations.mdx @@ -7,26 +7,25 @@ dates: posted: 2026-01-27 --- +## Overview + +Scaleway File Storage performance (IOPS and throughput) scales linearly with your provisioned capacity. To avoid bottleneck, you must pair your file system with Instances that matches its performance profile and supports the required number of mount points. -Overview -Scaleway File Storage performance (IOPS and Throughput) scales linearly with your provisioned capacity. To ensure your compute resources don't become a bottleneck, it is essential to pair your storage volume with an Instance type that matches its performance profile and supports the required number of mount points. -1. The Performance-to-Capacity Correlation Our File Storage architecture follows a "pay-as-you-grow" performance model: IOPS: Increase as you provision more GBs, up to the instance’s network limit. Throughput: Higher provisioning unlocks greater bandwidth for data-intensive read/write operations. -## Use cases +## Selecting the right file system capacity for your Instance -To optimize your ROI and avoid "throttling" your storage at the instance level, follow these guidelines based on your provisioned capacity. +To optimize storage costs and avoid throttling your file system at the Instance level, refer the use cases below to provision a file system with capacity adapted to your requirements. -### Light web applications and development environments +### Lightweight applications and development environments -Best For: Small web servers, dev/test environments, and low-traffic repositories. +Small web servers, development and testing environments, low-traffic repositories. - Provisioning Range: 25 GB to 100 GB -- Recommended Instance: POP2-2C (or any 2 vCPU General Purpose instance), BASIC3-X, BASIC2 - -Note: Ideal for 1 or 2 mount points to maintain a stable network baseline. +- Recommended Instance: POP2-2C (or any 2 vCPU General Purpose Instance), BASIC3-X, BASIC2 +- Ideal for 1 or 2 mount points to maintain a stable network baseline. ### Business applications and production environments @@ -38,7 +37,7 @@ Advantage: These instances provide the necessary network overhead to handle the ### High-Performance and data intensive workloads Provisioning Range: Above 1 TB -Recommended Instances: All GPU Instances or CPU 8C, 16C and above. +Recommended Instances: any GPU Instances or CPU 8C, 16C and above. Best For: AI/ML Fine-tuning and Inference, Video Encoding, Throughput intensive applications. Why: At 1 TB+, File Storage delivers significant throughput. Only high-core count or GPU instances have the network "pipe" required to ingest this level of data without latency. @@ -52,33 +51,69 @@ You can find the maximum number of file systems you can attach to a Scaleway Ins scw instance server-type list zone=fr-par-2 ``` -| NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS | -|------------------|-----|-----|---------|--------|------------------| -| L4-1-24G | 8 | 1 | 48 GiB | x86_64 | 2 | -| L4-2-24G | 16 | 2 | 96 GiB | x86_64 | 4 | -| L4-4-24G | 32 | 4 | 192 GiB | x86_64 | 8 | -| L4-8-24G | 64 | 8 | 384 GiB | x86_64 | 16 | -| POP2-HC-2C-4G | 2 | 0 | 4.0 GiB | x86_64 | 1 | -| POP2-2C-8G | 2 | 0 | 8.0 GiB | x86_64 | 1 | -| POP2-HM-2C-16G | 2 | 0 | 16 GiB | x86_64 | 2 | -| POP2-HC-4C-8G | 4 | 0 | 8.0 GiB | x86_64 | 1 | -| POP2-4C-16G | 4 | 0 | 16 GiB | x86_64 | 1 | -| POP2-HM-4C-32G | 4 | 0 | 32 GiB | x86_64 | 1 | -| POP2-HC-8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 | -| POP2-HN-3 | 2 | 0 | 4.0 GiB | x86_64 | 1 | -| POP2-8C-32G | 8 | 0 | 32 GiB | x86_64 | 2 | -| POP2-HM-8C-64G | 8 | 0 | 64 GiB | x86_64 | 2 | -| POP2-HC-16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 | -| POP2-HN-5 | 4 | 0 | 8.0 GiB | x86_64 | 1 | -| POP2-16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 | -| POP2-HN-10 | 4 | 0 | 8.0 GiB | x86_64 | 1 | -| POP2-HM-16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 | -| POP2-HC-32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 | -| POP2-32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 | -| POP2-HC-48C-96G | 48 | 0 | 96 GiB | x86_64 | 12 | -| POP2-HM-32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 | -| POP2-HC-64C-128G | 64 | 0 | 128 GiB | x86_64 | 16 | -| POP2-48C-192G | 48 | 0 | 192 GiB | x86_64 | 12 | -| POP2-64C-256G | 64 | 0 | 256 GiB | x86_64 | 16 | -| POP2-HM-48C-384G | 48 | 0 | 384 GiB | x86_64 | 12 | -| POP2-HM-64C-512G | 64 | 0 | 512 GiB | x86_64 | 16 | +| NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS | +|---------------------|-----|-----|---------|--------|------------------| +| BASIC3-X2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 | +| BASIC3-X2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 | +| BASIC3-X4C-8G | 4 | 0 | 8 GiB | x86_64 | 1 | +| COMPUTE3-X2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 | +| MEMORY3-X2C-16G | 2 | 0 | 16 GiB | x86_64 | 1 | +| POP2-HC-2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 | +| POP2-2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 | +| POP2-HC-4C-8G | 4 | 0 | 8 GiB | x86_64 | 1 | +| POP2-4C-16G | 4 | 0 | 16 GiB | x86_64 | 1 | +| POP2-HM-4C-32G | 4 | 0 | 32 GiB | x86_64 | 1 | +| POP2-HN-3 | 2 | 0 | 4 GiB | x86_64 | 1 | +| POP2-HN-5 | 4 | 0 | 8 GiB | x86_64 | 1 | +| POP2-HN-10 | 4 | 0 | 8 GiB | x86_64 | 1 | +| STANDARD2-A2C-8G | 2 | 0 | 8 GiB | arm64 | 1 | +| STANDARD3-X2C-8G | 2 | 0 | 8 GiB | x86_64 | 1 | +| BASIC3-X4C-16G | 4 | 0 | 16 GiB | x86_64 | 2 | +| BASIC3-X8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 | +| COMPUTE3-X4C-8G | 4 | 0 | 8 GiB | x86_64 | 2 | +| L4-1-24G | 8 | 1 | 48 GiB | x86_64 | 2 | +| MEMORY3-X4C-32G | 4 | 0 | 32 GiB | x86_64 | 2 | +| POP2-HM-2C-16G | 2 | 0 | 16 GiB | x86_64 | 2 | +| POP2-HC-8C-16G | 8 | 0 | 16 GiB | x86_64 | 2 | +| POP2-8C-32G | 8 | 0 | 32 GiB | x86_64 | 2 | +| POP2-HM-8C-64G | 8 | 0 | 64 GiB | x86_64 | 2 | +| STANDARD2-A4C-16G | 4 | 0 | 16 GiB | arm64 | 2 | +| STANDARD3-X4C-16G | 4 | 0 | 16 GiB | x86_64 | 2 | +| BASIC3-X8C-32G | 8 | 0 | 32 GiB | x86_64 | 4 | +| BASIC3-X16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 | +| COMPUTE3-X8C-16G | 8 | 0 | 16 GiB | x86_64 | 4 | +| COMPUTE3-X16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 | +| L4-2-24G | 16 | 2 | 96 GiB | x86_64 | 4 | +| MEMORY3-X8C-64G | 8 | 0 | 64 GiB | x86_64 | 4 | +| MEMORY3-X16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 | +| POP2-HC-16C-32G | 16 | 0 | 32 GiB | x86_64 | 4 | +| POP2-16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 | +| POP2-HM-16C-128G | 16 | 0 | 128 GiB | x86_64 | 4 | +| STANDARD2-A8C-32G | 8 | 0 | 32 GiB | arm64 | 4 | +| STANDARD2-A16C-64G | 16 | 0 | 64 GiB | arm64 | 4 | +| STANDARD3-X8C-32G | 8 | 0 | 32 GiB | x86_64 | 4 | +| STANDARD3-X16C-64G | 16 | 0 | 64 GiB | x86_64 | 4 | +| BASIC3-X16C-64G | 16 | 0 | 64 GiB | x86_64 | 8 | +| COMPUTE3-X32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 | +| COMPUTE3-X48C-96G | 48 | 0 | 96 GiB | x86_64 | 8 | +| COMPUTE3-X64C-128G | 64 | 0 | 128 GiB | x86_64 | 8 | +| COMPUTE3-X96C-192G | 96 | 0 | 192 GiB | x86_64 | 8 | +| L4-4-24G | 32 | 4 | 192 GiB | x86_64 | 8 | +| MEMORY3-X32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 | +| MEMORY3-X48C-384G | 48 | 0 | 384 GiB | x86_64 | 8 | +| POP2-HC-32C-64G | 32 | 0 | 64 GiB | x86_64 | 8 | +| POP2-32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 | +| POP2-HM-32C-256G | 32 | 0 | 256 GiB | x86_64 | 8 | +| STANDARD2-A32C-128G | 32 | 0 | 128 GiB | arm64 | 8 | +| STANDARD2-A48C-192G | 48 | 0 | 192 GiB | arm64 | 8 | +| STANDARD2-A64C-256G | 64 | 0 | 256 GiB | arm64 | 8 | +| STANDARD3-X32C-128G | 32 | 0 | 128 GiB | x86_64 | 8 | +| STANDARD3-X48C-192G | 48 | 0 | 192 GiB | x86_64 | 8 | +| STANDARD3-X64C-256G | 64 | 0 | 256 GiB | x86_64 | 8 | +| POP2-HC-48C-96G | 48 | 0 | 96 GiB | x86_64 | 12 | +| POP2-48C-192G | 48 | 0 | 192 GiB | x86_64 | 12 | +| POP2-HM-48C-384G | 48 | 0 | 384 GiB | x86_64 | 12 | +| L4-8-24G | 64 | 8 | 384 GiB | x86_64 | 16 | +| POP2-HC-64C-128G | 64 | 0 | 128 GiB | x86_64 | 16 | +| POP2-64C-256G | 64 | 0 | 256 GiB | x86_64 | 16 | +| POP2-HM-64C-512G | 64 | 0 | 512 GiB | x86_64 | 16 | \ No newline at end of file From 8da74de87252d4cb7efdc42cfad5dc448e92658d Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Wed, 8 Apr 2026 15:32:33 +0200 Subject: [PATCH 3/7] docs(file): update --- .../reference-content/limitations.mdx | 43 ++++++++++++------- 1 file changed, 27 insertions(+), 16 deletions(-) diff --git a/pages/file-storage/reference-content/limitations.mdx b/pages/file-storage/reference-content/limitations.mdx index 7c110ec64c..a1581427c2 100644 --- a/pages/file-storage/reference-content/limitations.mdx +++ b/pages/file-storage/reference-content/limitations.mdx @@ -1,7 +1,7 @@ --- title: File Storage and Instances selection guidelines description: This page explains how to provision the right file system for your Instance based on your use case. -tags: limits limitations scaleway file storage file system +tags: instances file sizing provisioning file system scaling dates: validation: 2026-01-27 posted: 2026-01-27 @@ -15,31 +15,42 @@ Our File Storage architecture follows a "pay-as-you-grow" performance model: IOPS: Increase as you provision more GBs, up to the instance’s network limit. Throughput: Higher provisioning unlocks greater bandwidth for data-intensive read/write operations. -## Selecting the right file system capacity for your Instance +## Selecting the right file system capacity for your Instance -To optimize storage costs and avoid throttling your file system at the Instance level, refer the use cases below to provision a file system with capacity adapted to your requirements. +To optimize storage costs and avoid throttling your file system at the Instance level, refer to the use cases below to provision a file system with capacity adapted to your requirements. ### Lightweight applications and development environments -Small web servers, development and testing environments, low-traffic repositories. +Ideal for small web servers, development and testing environments, low-traffic repositories. -- Provisioning Range: 25 GB to 100 GB -- Recommended Instance: POP2-2C (or any 2 vCPU General Purpose Instance), BASIC3-X, BASIC2 -- Ideal for 1 or 2 mount points to maintain a stable network baseline. +- **Provisioning range:** 25 GB to 100 GB +- **Recommended instances:** POP2-2C (or any 2 vCPU General Purpose Instance), BASIC3-X, BASIC2 + + +Ideal for one or two mount points to maintain a stable network baseline. + ### Business applications and production environments -Provisioning Range: 100 GB to 500 GB -Recommended Instances: POP2-4C / STANDARD3-X4C -Best For: Medium-sized CMS Web applications, application servers, and corporate media file sharing, CI/CD runner cache sharing -Advantage: These instances provide the necessary network overhead to handle the increased throughput of mid-range storage. +Ideal for medium-sized CMS web applications, application servers, corporate media file sharing, CI/CD runner cache sharing. + +- **Provisioning range:** 100 GB to 500 GB +- **Recommended instances:** POP2-4C, STANDARD3-X4C + + +These Instances provide the necessary network overhead to handle the increased throughput of mid-range storage. + + +### High-performance and data-intensive workloads + +Ideal for AI/ML fine-tuning and inference, video encoding, throughput-intensive applications. -### High-Performance and data intensive workloads +- **Provisioning range:** Above 1 TB +- **Recommended instances:** Any GPU instance, or CPU instances with 8 cores or more. -Provisioning Range: Above 1 TB -Recommended Instances: any GPU Instances or CPU 8C, 16C and above. -Best For: AI/ML Fine-tuning and Inference, Video Encoding, Throughput intensive applications. -Why: At 1 TB+, File Storage delivers significant throughput. Only high-core count or GPU instances have the network "pipe" required to ingest this level of data without latency. + +Above 1 TB, File Storage delivers significant throughput. Only high-core count or GPU instances have the network capacity required to ingest this level of data without latency. + ## File system attachements per Instance type From 426d532783919293d7933569cef13921cfeddcb1 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Wed, 8 Apr 2026 17:52:29 +0200 Subject: [PATCH 4/7] docs(file): update --- pages/file-storage/menu.ts | 8 +++- ...mdx => file-system-instance-selection.mdx} | 6 +-- .../reference-content/performance-scaling.mdx | 44 +++++++++++++++++++ 3 files changed, 51 insertions(+), 7 deletions(-) rename pages/file-storage/reference-content/{limitations.mdx => file-system-instance-selection.mdx} (96%) create mode 100644 pages/file-storage/reference-content/performance-scaling.mdx diff --git a/pages/file-storage/menu.ts b/pages/file-storage/menu.ts index 0f4ae716e6..7b370d8fcf 100644 --- a/pages/file-storage/menu.ts +++ b/pages/file-storage/menu.ts @@ -63,8 +63,12 @@ export const fileStorageMenu = { { items: [ { - label:'File Storage limitations', - slug:'limitations' + label:'File Storage and Instances guidelines', + slug:'file-system-instance-selection' + }, + { + label:'Performance scaling', + slug:'performance-scaling' }, ], label:'Additional content', diff --git a/pages/file-storage/reference-content/limitations.mdx b/pages/file-storage/reference-content/file-system-instance-selection.mdx similarity index 96% rename from pages/file-storage/reference-content/limitations.mdx rename to pages/file-storage/reference-content/file-system-instance-selection.mdx index a1581427c2..d456ca1fcf 100644 --- a/pages/file-storage/reference-content/limitations.mdx +++ b/pages/file-storage/reference-content/file-system-instance-selection.mdx @@ -7,13 +7,9 @@ dates: posted: 2026-01-27 --- -## Overview - Scaleway File Storage performance (IOPS and throughput) scales linearly with your provisioned capacity. To avoid bottleneck, you must pair your file system with Instances that matches its performance profile and supports the required number of mount points. -Our File Storage architecture follows a "pay-as-you-grow" performance model: -IOPS: Increase as you provision more GBs, up to the instance’s network limit. -Throughput: Higher provisioning unlocks greater bandwidth for data-intensive read/write operations. +Refer to the [dedicated documentation](/file-storage/reference-content/performance-scaling/) for more information on performance scaling. ## Selecting the right file system capacity for your Instance diff --git a/pages/file-storage/reference-content/performance-scaling.mdx b/pages/file-storage/reference-content/performance-scaling.mdx new file mode 100644 index 0000000000..1ce981c750 --- /dev/null +++ b/pages/file-storage/reference-content/performance-scaling.mdx @@ -0,0 +1,44 @@ +--- +title: File Storage performance scaling +description: This page explains how throughput and IOPS of a file system scale with provisioned capacity when using Scaleway File Storage. +tags: instances file sizing provisioning file system scaling +dates: + validation: 2026-04-08 + posted: 2026-04-08 +--- + +## Performance scaling + +Scaleway File Storage architecture follows a "pay-as-you-grow" model where IOPS and throughput scale linearly as you provision more capacity for a file system. This guarantees consistent and predictable performance that you can adjust according to your needs. + +Both IOPS and throughput reach their maximum values at 2 TB of provisioned capacity. Provisioning beyond 2 TB increases available storage, but does not further increase performance. + +### IOPS + +Baseline +: 1,000 IOPS at 25 GB + +Scaling rate +: +12 IOPS per provisioned GB + +Maximum +: 25,000 IOPS at 2 TB + +IOPS scale linearly between the baseline and the maximum. Beyond 2 TB of provisioned capacity, IOPS remain capped at 25,000. + +**Example:** A file system provisioned with 100 GB delivers approximately 1,900 IOPS (1,000 + 75 * 12). + +### Throughput + +Baseline +: 4 MB/s at 25 GB + +Scaling rate +: +0.1 MB/s per provisioned GB + +Maximum +: 200 MB/s at 2 TB + +Throughput scales linearly between the baseline and the maximum. Beyond 2 TB of provisioned capacity, throughput remains capped at 200 MB/s. + +**Example:** A file system provisioned with 100 GB delivers approximately 11.5 MB/s (4 + 75 * 0.1). \ No newline at end of file From 39a52b10fdbf6867b673a3a04d76a68a6d89e70e Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 9 Apr 2026 14:15:29 +0200 Subject: [PATCH 5/7] docs(file): update --- .../reference-content/file-system-instance-selection.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/file-storage/reference-content/file-system-instance-selection.mdx b/pages/file-storage/reference-content/file-system-instance-selection.mdx index d456ca1fcf..7935e47e28 100644 --- a/pages/file-storage/reference-content/file-system-instance-selection.mdx +++ b/pages/file-storage/reference-content/file-system-instance-selection.mdx @@ -48,7 +48,7 @@ Ideal for AI/ML fine-tuning and inference, video encoding, throughput-intensive Above 1 TB, File Storage delivers significant throughput. Only high-core count or GPU instances have the network capacity required to ingest this level of data without latency. -## File system attachements per Instance type +## File system attachments per Instance type To ensure optimum performance, the number of file systems you can attach to an Instance is limited based on the Instance's configuration. @@ -58,6 +58,10 @@ You can find the maximum number of file systems you can attach to a Scaleway Ins scw instance server-type list zone=fr-par-2 ``` + +The availability of Instances types varies between Availability Zones, some offers may be missing in the table below. + + | NAME | CPU | GPU | RAM | ARCH | MAX FILE SYSTEMS | |---------------------|-----|-----|---------|--------|------------------| | BASIC3-X2C-4G | 2 | 0 | 4 GiB | x86_64 | 1 | From 0b827329ab1c9e9d8aa47e841c190e0b262d149f Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 9 Apr 2026 14:16:25 +0200 Subject: [PATCH 6/7] docs(file): update --- pages/file-storage/menu.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/file-storage/menu.ts b/pages/file-storage/menu.ts index 7b370d8fcf..bf2b4b7120 100644 --- a/pages/file-storage/menu.ts +++ b/pages/file-storage/menu.ts @@ -63,7 +63,7 @@ export const fileStorageMenu = { { items: [ { - label:'File Storage and Instances guidelines', + label:'File Storage and Instances selection', slug:'file-system-instance-selection' }, { From 58ee9c399f608410f02487cb863e7f74dda967cc Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Thu, 9 Apr 2026 16:12:50 +0200 Subject: [PATCH 7/7] docs(file): update --- .../file-system-instance-selection.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/file-storage/reference-content/file-system-instance-selection.mdx b/pages/file-storage/reference-content/file-system-instance-selection.mdx index 7935e47e28..dc09bffa8e 100644 --- a/pages/file-storage/reference-content/file-system-instance-selection.mdx +++ b/pages/file-storage/reference-content/file-system-instance-selection.mdx @@ -7,17 +7,17 @@ dates: posted: 2026-01-27 --- -Scaleway File Storage performance (IOPS and throughput) scales linearly with your provisioned capacity. To avoid bottleneck, you must pair your file system with Instances that matches its performance profile and supports the required number of mount points. +Scaleway File Storage performance (IOPS and throughput) scales linearly with your provisioned capacity. To avoid bottlenecks, you must pair your file system with Instances that matches its performance profile and supports the required number of mount points. Refer to the [dedicated documentation](/file-storage/reference-content/performance-scaling/) for more information on performance scaling. -## Selecting the right file system capacity for your Instance +## Select the right file system capacity for your Instance To optimize storage costs and avoid throttling your file system at the Instance level, refer to the use cases below to provision a file system with capacity adapted to your requirements. -### Lightweight applications and development environments +### Small-scale applications and production environments -Ideal for small web servers, development and testing environments, low-traffic repositories. +Ideal for lightweight web servers, small-scale production environments, and low-traffic repositories. - **Provisioning range:** 25 GB to 100 GB - **Recommended instances:** POP2-2C (or any 2 vCPU General Purpose Instance), BASIC3-X, BASIC2 @@ -28,7 +28,7 @@ Ideal for one or two mount points to maintain a stable network baseline. ### Business applications and production environments -Ideal for medium-sized CMS web applications, application servers, corporate media file sharing, CI/CD runner cache sharing. +Ideal for medium-sized CMS web applications, application servers, corporate media file sharing, and CI/CD runner cache sharing. - **Provisioning range:** 100 GB to 500 GB - **Recommended instances:** POP2-4C, STANDARD3-X4C @@ -39,7 +39,7 @@ These Instances provide the necessary network overhead to handle the increased t ### High-performance and data-intensive workloads -Ideal for AI/ML fine-tuning and inference, video encoding, throughput-intensive applications. +Ideal for AI/ML fine-tuning and inference, video encoding, and throughput-intensive applications. - **Provisioning range:** Above 1 TB - **Recommended instances:** Any GPU instance, or CPU instances with 8 cores or more. @@ -52,7 +52,7 @@ Above 1 TB, File Storage delivers significant throughput. Only high-core count o To ensure optimum performance, the number of file systems you can attach to an Instance is limited based on the Instance's configuration. -You can find the maximum number of file systems you can attach to a Scaleway Instance using the following [Scaleway CLI](/scaleway-cli/quickstart/) command. Do not forget to replace the value of the `zone` parameter with the desired Availability Zone: +Use the following [Scaleway CLI](/scaleway-cli/quickstart/) command to find the maximum number of file systems you can attach to a Scaleway Instance. Do not forget to replace the value of the `zone` parameter with the desired Availability Zone: ```bash scw instance server-type list zone=fr-par-2