Skip to content

feat(ins): add slo #5423

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
merged 3 commits into from
Aug 26, 2025
Merged

feat(ins): add slo #5423

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c3e05d3
feat(ins): add slo
bene2k1 Aug 19, 2025
ae68dc3
feat(gpu): add gpu slo
bene2k1 Aug 19, 2025
47991f6
Apply suggestions from code review
bene2k1 Aug 26, 2025
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
4 changes: 4 additions & 0 deletions pages/gpu/reference-content/choosing-gpu-instance-type.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,10 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t
| Use cases | GenAI (Image/Video) | GenAI (Image/Video) | 7B Text-to-image model fine-tuning / Inference | 70B text-to-image model fine-tuning / Inference |
| What they are not made for | | | | |

<Message type="note">
The service level objective (SLO) for all GPU Instance types is 99.5% availability.
</Message>

### Scaleway AI Supercomputer
| | **[Custom build clusters](https://www.scaleway.com/en/ai-supercomputers/)** (2DGX H100, 16 H100 GPUs) | **[Custom build clusters](https://www.scaleway.com/en/ai-supercomputers/)** (127 DGX H100, 1016 H100 GPUs) |
|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
Expand Down
8 changes: 7 additions & 1 deletion pages/instances/reference-content/instances-datasheet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ This datasheet provides a concise overview of the performance, technical feature
| Resources | Shared vCPUs |
| Sizing | 1 vCPU, 1 GiB RAM |
| vCPU:RAM ratio | 1:1 |
| SLA | None |
| SLO | None |

## Development and General Purpose Instances

Expand All @@ -45,6 +45,7 @@ See below the technical specifications of Development and General Purpose Instan
| Resources | Shared vCPUs |
| Sizing | From 2 to 4 vCPUs <br />From 2 to 12 GiB RAM |
| vCPU:RAM ratio | Various<br />(1:1, 1:2, 1:3) |
| SLO | None |

## PLAY2 and PRO2 Instances

Expand All @@ -61,6 +62,7 @@ See below the technical specifications of PLAY2 and PRO2 Instances:
| Resources | Shared vCPUs |
| Sizing | From 1 to 32 vCPUs <br />From 2 to 128 GiB RAM |
| vCPU:RAM ratio | Various<br />(1:2, 1:4) |
| SLO | None |

## COP-ARM Instances

Expand All @@ -77,6 +79,7 @@ The table below displays the technical specifications of COP-ARM Instances:
| Resources | Shared vCPUs |
| Sizing | From 2 to 128 vCPUs <br />From 8 to 128 GiB RAM |
| vCPU:RAM ratio | 1:4 |
| SLO | None |

## Enterprise Instances

Expand All @@ -94,6 +97,7 @@ See below the technical specifications of Enterprise Instances:
| Security feature | Secure Encrypted Virtualization |
| Sizing | From 2 to 96 vCPUs <br /> From 8 GiB to 384 GiB RAM |
| vCPU:RAM ratio | 1:4 |
| SLO | None |

\* 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.

Expand All @@ -112,6 +116,7 @@ See below the technical specifications of Production-Optimized Instances:
| Resources | Dedicated vCPUs* |
| Sizing | From 2 to 96 vCPUs <br /> From 8 GiB to 384 GiB RAM |
| vCPU:RAM ratio | 1:4 |
| SLO | 99.5% availability |

\* 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.

Expand All @@ -134,5 +139,6 @@ See below the technical specifications of Workload-Optimized Instances:
| Security feature | Secure Encrypted Virtualization |
| Sizing | From 2 to 64 dedicated vCPUs <br /> From 4 GiB to 512 GiB RAM |
| vCPU:RAM ratio | 1:8 (POP2-HM), 1:2 (POP2-HC and POP2-HN) |
| SLO | 99.5% availability |

\* 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.
Loading