Skip to content

fix(efc): update ins with gpu #5822

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+9 −4
Open

fix(efc): update ins with gpu #5822

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6cb707
fix(efc): update ins with gpu
ldecarvalho-doc Nov 17, 2025
33b0568
fix(efc): review elise
ldecarvalho-doc Nov 18, 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
13 changes: 9 additions & 4 deletions pages/environmental-footprint/additional-content/instances-env-footprint.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ dates:
validation: 2025-10-01
posted: 2025-05-27
---
import image from './assets/scaleway-allocation-rules-instances.webp'
import image from './assets/scaleway-allocation-rules-instances.jpg'


## Console overview
Expand All @@ -19,8 +19,8 @@ For Virtual Instances, the calculation of the environmental footprint takes into
## Calculation aspects

The following elements are considered in the Instance footprint calculation:
- **Hypervisor resources** - the resources (CPU, RAM, and disk, for example) used in the physical hypervisor servers that create and run the virtual Instances.
- **Instance offer resources** - the vCPU, RAM, and disk resources used when you use an Instance.
- **Hypervisor resources** - the resources (CPU, GPU, RAM, and disk, for example) used in the physical hypervisor servers that create and run the virtual Instances.
- **Instance offer resources** - the vCPU, GPU, RAM, and disk resources used when you use an Instance.

The calculation using the elements above can be broken down into:

Expand All @@ -43,7 +43,8 @@ The calculation using the elements above can be broken down into:

When calculating an Instance's footprint, we consider the resources based on their relative usage on the hypervisor to ensure an accurate distribution of their proportional consumption.

- **CPU** - Consider the share of vCPUs reserved compared to the total number of physical cores available.
- **CPUs** - Consider the share of vCPUs reserved compared to the total number of physical cores available.
- **GPUs** - Consider the share of GPUs reserved compared to the total number of physical cores available.
- **RAM** - Consider the share of allocated RAM compared to the total RAM of the hypervisor.
- **Storage** - Consider the use of allocated storage compared to the total capacity of the hypervisor.

Expand All @@ -65,6 +66,10 @@ A consumption profile is a formula that takes in a given workload (e.g. % CPU us

We use the [consumption profiles defined by Boavizta](https://doc.api.boavizta.org/Reference/routes/#consumption-profile-routes) for the CPUs used on Scaleway Instances.

<Message type="important">
Boavizta consumption profiles are currently only available for CPU Instances. Electricity consumption for GPU Instances is calculated based on an average consumption of the GPU offers.
</Message>

For the [Environmental Footprint Estimation](/environmental-footprint/additional-content/environmental-footprint-calculator-estimation/), we base the calculation on a theoretical value of 30% CPU usage. On your [monthly report](/environmental-footprint/how-to/track-monthly-footprint/), we use your real CPU consumption to provide you with the most reliable data possible.

### Calculation example
Expand Down
Loading