Skip to content

feat(efc): add instances metho MTA-5653 #4971

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Conversation

ldecarvalho-doc
Copy link
Contributor

No description provided.

@ldecarvalho-doc ldecarvalho-doc self-assigned this May 14, 2025
@ldecarvalho-doc ldecarvalho-doc added type: new content New pages or categories do not merge PR that shouldn't be merged before a specific date (eg release) status: tech review Waiting for technical review status: doc review Waiting for doc team review labels May 14, 2025
- **CPU** - Consider the share of vCPUs 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.
</Concept>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we shoud add the calculation here and may be an exemple (cf https://confluence.infra.online.net/spaces/EFP/pages/252921608/Instance+methodologie+-+Estimation)
We should also explain that we take into account the real use of the instances via the CPU usage and the consumption profiles defined by boavizta (cf https://confluence.infra.online.net/spaces/EFP/pages/252921883/Instance+methodologie+-+Usage#InstancemethodologieUsage-Version2-Consumptionprofiles)

@@ -771,6 +771,14 @@
{
"label": "Understanding your environmental footprint estimation",
"slug": "environmental-footprint-calculator-estimation"
},
{
"label": "Bare Metal Footprint Calculation",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"label": "Bare Metal Footprint Calculation",
"label": "Bare Metal footprint calculation",

not sure but I guess no uppercase here?

"slug": "bare-metal-env-footprint"
},
{
"label": "Instances Footprint Calculation",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"label": "Instances Footprint Calculation",
"label": "Instances footprint calculation",

ldecarvalho-doc and others added 3 commits May 27, 2025 15:38
Co-authored-by: Benedikt Rollik <brollik@scaleway.com>
posted: 2025-05-27
categories:
- environmental-footprint
- bare-metal

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be we should precise that bare-metal = Elastic Metal and Apple silicon (and soon Dedibox)

ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e
```

Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example explain how the manufacturing impact is calculated but not the use. For the use, we will have :
server_power_consumption x usage_duration x energy_mix x DC_PUE

So for this exemple with an Elastic Metal with a power of 110w, use for 100 hour in DC5 (french energy mix = O,056kgCo2e/kwh and dc PUE = 1,16) we will have :
0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e

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

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add this to the bare metal server page too. It's a good summary of environmental footprint calculation breakdown.


To obtain an accurate calculation of the Instance's footprint, we multiply the results in each step of the [basis calculation](/environmental-footprint/additional-content/environmental-footprint-calculator/), bar the Cross-IT equipment & stock calculations step, by the `Resources_Used_VM` ratio.

## Cross-IT equipment & stock calculation for Instances

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no "special" calculation for Instance stock


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.

Initially we base the calculation on a [theoretical value](https://doc.api.boavizta.org/Explanations/components/cpu/#usage-impacts) of 30% CPU usage.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


### Calculation example

In the example below we will calculate the manufacturing impact allocated to an Instance for a one-year usage period.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not do an exemple for 100hour usage like bare metal ?


```
1 / 6 x 100 x 0,425 = 7,1 kgCO2eq
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add an exemple for the usage impact too ?

for a 100hour usage period of an instance in FR-PAR-2 with a mean of 40% for CPU usage.
in Boavizta we can get that 40% usage of a specific CPU is for exemple 80w, french energy mix is 0,056kgCo2e/kwh and dc PUE is 1.16 so we have :
0,080 x 100 x 0,056 x 1.16 = 0,52 kgCo2e

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
do not merge PR that shouldn't be merged before a specific date (eg release) status: doc review Waiting for doc team review status: tech review Waiting for technical review type: new content New pages or categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants