Skip to content

docs(file): Add instances compatibility, scaling and listing #6394

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SamyOubouaziz merged 7 commits into from
Apr 10, 2026
Merged

docs(file): Add instances compatibility, scaling and listing #6394

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a620d67
docs(file): update
SamyOubouaziz Apr 8, 2026
cf7c395
docs(file): update
SamyOubouaziz Apr 8, 2026
8da74de
docs(file): update
SamyOubouaziz Apr 8, 2026
426d532
docs(file): update
SamyOubouaziz Apr 8, 2026
39a52b1
docs(file): update
SamyOubouaziz Apr 9, 2026
0b82732
docs(file): update
SamyOubouaziz Apr 9, 2026
58ee9c3
docs(file): update
SamyOubouaziz Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions pages/file-storage/menu.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,12 @@ export const fileStorageMenu = {
{
items: [
{
label:'File Storage limitations',
slug:'limitations'
label:'File Storage and Instances selection',
slug:'file-system-instance-selection'
},
{
label:'Performance scaling',
slug:'performance-scaling'
},
],
label:'Additional content',
Expand Down
130 changes: 130 additions & 0 deletions pages/file-storage/reference-content/file-system-instance-selection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,130 @@
---
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: instances file sizing provisioning file system scaling
dates:
validation: 2026-01-27
posted: 2026-01-27
---

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.

## 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.

### Small-scale applications and production environments

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

<Message type="tip">
Ideal for one or two mount points to maintain a stable network baseline.
</Message>

### Business applications and production environments

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

<Message type="tip">
These Instances provide the necessary network overhead to handle the increased throughput of mid-range storage.
</Message>

### High-performance and data-intensive workloads

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.

<Message type="tip">
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.
</Message>

## 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.

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
```

<Message type="note">
The availability of Instances types varies between Availability Zones, some offers may be missing in the table below.
</Message>

| 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 |
50 changes: 0 additions & 50 deletions pages/file-storage/reference-content/limitations.mdx
View file
Open in desktop

This file was deleted.

44 changes: 44 additions & 0 deletions pages/file-storage/reference-content/performance-scaling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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).
Loading