Skip to content

fix(ins): remove outdated information #5612

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 1 commit into from
Oct 6, 2025
Merged

fix(ins): remove outdated information #5612

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 1 addition & 2 deletions pages/instances/reference-content/instances-datasheet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,10 +122,9 @@ See below the technical specifications of Specialized Instances:
| CPU type | AMD EPYC 7543 (2,8 GHz) |
| CPU architecture | `amd64` |
| Resources | Dedicated vCPUs* |
| 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](https://www.scaleway.com/en/virtual-instances/sla/) | 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.
\* 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.