Skip to content

Commit e9bc270

Browse files
ldecarvalho-docldecarvalho-doc
authored
feat(efc): add instances metho MTA-5653 (#4971)
1 parent 814df09 commit e9bc270

8 files changed

+244
-28
lines changed

‎menu/navigation.json

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -274,16 +274,28 @@
274274
{
275275
"items": [
276276
{
277-
"label": "Environmental Footprint calculation breakdown",
277+
"label": "Calculation breakdown",
278278
"slug": "environmental-footprint-calculator"
279279
},
280280
{
281-
"label": "Environmental footprint calculator product integration",
281+
"label": "Calculation reference values",
282+
"slug": "calculation-values-reference"
283+
},
284+
{
285+
"label": "Calculator product integration",
282286
"slug": "environmental-footprint-integration"
283287
},
284288
{
285289
"label": "Understanding your environmental footprint estimation",
286290
"slug": "environmental-footprint-calculator-estimation"
291+
},
292+
{
293+
"label": "Bare Metal footprint calculation",
294+
"slug": "bare-metal-env-footprint"
295+
},
296+
{
297+
"label": "Instances footprint calculation",
298+
"slug": "instances-env-footprint"
287299
}
288300
],
289301
"label": "Additional Content",

‎pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-instances.webp

156 KB
Binary file not shown.

‎pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
meta:
3+
title: Bare Metal footprint calculation
4+
description: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail.
5+
content:
6+
h1: Bare Metal footprint calculation
7+
paragraph: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail.
8+
tags: bare-metal environmental-footprint impact datacentre
9+
dates:
10+
validation: 2025-05-27
11+
posted: 2025-05-27
12+
categories:
13+
- environmental-footprint
14+
- bare-metal
15+
---
16+
17+
At Scaleway the Bare Metal category includes different types of servers, such as:
18+
- Apple silicon servers
19+
- Elastic Metal servers, and
20+
- Dedibox servers.
21+
22+
This page includes the specificities of the environmental footprint calculation for Apple silicon and Elastic Metal servers.
23+
24+
<Message type="important">
25+
The calculations also take into consideration all the elements described in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/) documentation page. Refer to said page for a full breakdown of the Environmental Footprint calculation performed at Scaleway.
26+
</Message>
27+
28+
For bare metal servers, the allocation of environmental impact is straightforward due to the direct association between a user and a server. The environmental impact of a bare metal server is entirely attributed to the user who operates it. This encompasses the energy consumption during its operation, as well as a portion of the impact from the server's manufacturing process.
29+
30+
The manufacturing impact is prorated based on the server's lifespan and the duration of its use by the customer. By dividing the total manufacturing impact by the expected lifetime of the server and then allocating it according to the specific usage period, we ensure that each user is accountable for their fair share of the server's overall environmental footprint.
31+
32+
<Lightbox src="scaleway-allocation-rules-customer-it-equip.webp" alt="" />
33+
34+
<Message type="important">
35+
Currently, our calculations for Elastic Metal GPU servers do not include the environmental impact of GPU manufacturing due to insufficient data from the manufacturer. While the impact of CPUs, RAM, disk, and energy consumption is accounted for, the absence of GPU manufacturing data means the figures provided today are underestimated.
36+
37+
We will update our methodology as soon as more reliable data on GPU manufacturing becomes available.
38+
</Message>
39+
40+
## Calculation example
41+
42+
For the use of an Elastic Metal server, with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, we make the following calculation:
43+
44+
```math
45+
ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e
46+
```
47+
48+
Therefore 1,62 kgCO2e is added to the total manufacturing impact of this server.
49+
50+
To calculate the usage, we consider the French energy mix and the datacenter's PUE. In this example, they are O,056kgCo2e/kwh and 1,16, respectively. Which results in:
51+
52+
```math
53+
UsageFootprint = 0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e
54+
```

‎pages/environmental-footprint/additional-content/calculation-values-reference.mdx

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
meta:
3+
title: Calculation reference values
4+
description: This page provides a reference for the calculation values used to estimate the environmental impact of Scaleway's infrastructure.
5+
content:
6+
h1: Calculation values reference
7+
paragraph: This page provides a central location for accessing the key values used in calculating the environmental footprint of Scaleway's services.
8+
tags: environmental-impact calculation-values datacenter reference
9+
dates:
10+
validation: 2025-06-09
11+
posted: 2025-06-09
12+
categories:
13+
- environmental-footprint
14+
- reference-values
15+
---
16+
17+
The values referenced below are the ones used by Scaleway in the [Environmental Footprint calculation](/environmental-footprint/additional-content/environmental-footprint-calculator).
18+
19+
## Energy mix
20+
| Country | Energy Mix (kgCO2e/kWh) |
21+
| --- | --- |
22+
| France | 0.056 |
23+
| Netherlands | 0.268 |
24+
| Poland | 0.661 |
25+
26+
**Source**: [Ember](https://ember-climate.org/)
27+
28+
29+
## Datacenter PUE/WUE
30+
31+
| Datacenter | PUE | WUE |
32+
| --- | --- | --- |
33+
| fr-par-1 | 1.46 | 0.014 |
34+
| fr-par-2 | 1.16 | 0.214 |
35+
| fr-par-3 | 1.44 | 0.004 |
36+
| nl-ams-1 | 1.38 | 0.85 |
37+
| nl-ams-2 | 1.4 | NA |
38+
| nl-ams-3 | 1.2 | NA |
39+
| pl-waw-1 | 1.51 | NA |
40+
| pl-waw-2 | 1.32 | NA |
41+
| pl-waw-3 | 1.43 | NA |
42+
43+
**Sources**:
44+
- [FR-PAR-1](https://pue.dc2.opcore.eu/en/)
45+
- [FR-PAR-5](https://pue.dc5.opcore.eu/en/)
46+
47+
## Lifespan
48+
| Component | Lifespan (years) |
49+
| --- | --- |
50+
| Hardware | 6 |
51+
| Data Center | 25 |
52+
| Network Hardware Equipment | 10 |
53+
54+

‎pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx

Lines changed: 7 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ The details of the calculations for each of these elements are detailed below.
6565

6666
### Definition of the variables
6767

68-
<Lightbox src="scaleway-allocation-rules-dc-techenv-manuf.webp" alt="" />
69-
7068
All calculations will use the following variables:
7169

70+
<Lightbox src="scaleway-allocation-rules-dc-techenv-manuf.webp" alt="" />
71+
7272
<Message type="note">
7373
The acronyms used below are based on the French phrases for these terms.
7474
</Message>
@@ -114,31 +114,16 @@ For the use of network machines induced by your use of Scaleway products, we tak
114114

115115
To accurately calculate the environmental impact of each server used directly for Scaleway offers, we will implement specific allocation rules tailored to each product. These rules will ensure that the impact is precisely distributed according to the unique usage patterns and resource demands of different products.
116116

117-
Each product will have its own set of criteria to allocate the environmental footprint, considering factors such as server utilization rates, operational timeframes, and the specific technical requirements of the product. By customizing the allocation rules for each offering, we can ensure a more accurate and fair representation of the environmental impact associated with each product.
118-
119-
#### Bare Metal
117+
In the calculation pictured below we consider the formula for calculating the customer IT equipment impact allocation for Bare Metal servers.
120118

121119
<Lightbox src="scaleway-allocation-rules-customer-it-equip.webp" alt="" />
122120

123-
For bare metal servers, the allocation of environmental impact is straightforward due to the direct association between a user and a server. The environmental impact of a bare metal server is entirely attributed to the user utilizing it. This encompasses the energy consumption during its operation, as well as a portion of the impact from the server's manufacturing process.
124-
125-
The manufacturing impact is prorated based on the server's lifespan and the duration of its use by the customer. By dividing the total manufacturing impact by the expected lifetime of the server and then allocating it according to the specific usage period, we ensure that each user is accountable for their fair share of the server's overall environmental footprint.
126-
127-
<Message type="important">
128-
Currently, our calculations for Elastic Metal GPU servers do not include the environmental impact of GPU manufacturing due to insufficient data from the manufacturer. While the impact of CPUs, RAM, disk, and energy consumption is accounted for, the absence of GPU manufacturing data means the figures provided today are underestimated.
129-
130-
We will update our methodology as soon as more reliable data on GPU manufacturing becomes available.
131-
</Message>
132-
133-
#### Calculation example
134-
135-
For the use of an Elastic Metal server, with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, we make the following calculation:
121+
Each product will have its own set of criteria to allocate the environmental footprint, considering factors such as server utilization rates, operational timeframes, and the specific technical requirements of the product. By customizing the allocation rules for each offering, we can ensure a more accurate and fair representation of the environmental impact associated with each product.
136122

137-
```math
138-
ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e
139-
```
123+
You can find the calculation specifications for each of the available products in the list below:
140124

141-
Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server.
125+
- [Bare Metal](/environmental-footprint/additional-content/bare-metal-env-footprint)
126+
- [Instances](/environmental-footprint/additional-content/instances-env-footprint)
142127

143128
### Cross-IT equipment & stock
144129

‎pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,15 @@ The following tables provide details about the Scaleway products that currently
2626

2727
| **Product Name** | **Environmental Footprint calculator available** |
2828
|----------------------------|---------------------------------|
29-
| Dedibox | **Not integrated yet** |
30-
| Instances | **Not integrated yet** |
29+
| Dedibox | **Integration ongoing** |
30+
| Instances | **Integration ongoing** |
31+
| Block Storage | **Integration ongoing** |
3132
| GPU Instances | **Not integrated yet** |
3233
| Kubernetes | **Not integrated yet** |
3334
| Container Registry | **Not integrated yet** |
3435
| Managed Inference | **Not integrated yet** |
3536
| Generative APIs | **Not integrated yet** |
3637
| Object Storage | **Not integrated yet** |
37-
| Block Storage | **Not integrated yet** |
3838
| Managed Databases for PostgreSQL and MySQL | **Not integrated yet** |
3939
| Serverless Functions | **Not integrated yet** |
4040
| Serverless Containers | **Not integrated yet** |

‎pages/environmental-footprint/additional-content/instances-env-footprint.mdx

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
meta:
3+
title: Instances footprint calculation
4+
description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail.
5+
content:
6+
h1: Instances footprint calculation
7+
paragraph: This page explains how Scaleway calculates the environmental footprint of its Instances in detail.
8+
tags: instances environmental-footprint impact cloud-computing
9+
dates:
10+
validation: 2025-05-27
11+
posted: 2025-05-27
12+
categories:
13+
- environmental-footprint
14+
- instances
15+
---
16+
17+
For Virtual Instances, the calculation of the environmental footprint takes into consideration all the elements described on the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/) documentation page.
18+
19+
## Calculation aspects
20+
21+
The following elements are considered in the Instance footprint calculation:
22+
- **Hypervisor resources** - the resources (CPU, RAM, and disk, for example) used in the physical hypervisor servers that create and run the virtual Instances.
23+
- **Instance offer resources** - the vCPU, RAM, and disk resources used when you use an Instance.
24+
25+
The calculation using the elements above can be broken down into:
26+
27+
### Manufacturing Impact
28+
- Manufacturing of the underlying physical servers (hypervisors) necessary to run the Instances.
29+
- Distribution of the manufacturing impact according to the resources consumed by the Instance (vCPU, RAM, storage).
30+
31+
### Operational Impact
32+
- Energy consumption of the hypervisors during Instance usage.
33+
- [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts#pue-power-usage-effectiveness) specific to the data center where the Instance is hosted.
34+
- Energy mix of the country that provides the electricity.
35+
36+
### Usage Impact
37+
- Resources consumed by the Instance, calculated based on the material specifications of the hypervisors.
38+
39+
### Indirect Emissions
40+
- Impact related to cross-functional services necessary to guarantee the operation of the Instance, such as network and shared storage.
41+
42+
## Instance consumption ratio
43+
44+
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.
45+
46+
- **CPU** - Consider the share of vCPUs reserved compared to the total number of physical cores available.
47+
- **RAM** - Consider the share of allocated RAM compared to the total RAM of the hypervisor.
48+
- **Storage** - Consider the use of allocated storage compared to the total capacity of the hypervisor.
49+
50+
<Lightbox src="scaleway-allocation-rules-instances.webp" alt="" />
51+
52+
The value derived from this calculation will be used in every step of the calculation of the Instance's footprint. The variable is represented as `Resources_Used_VM` in the image above.
53+
54+
Refer to the table below to understand how the `Resources_Used_VM` is integrated into the calculation of each aspect of the total footprint calculation.
55+
56+
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.
57+
58+
## Cross-IT equipment calculation for Instances
59+
60+
The only part of the calculation that will differ from the basis is the [Customer Servers](/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers) section.
61+
62+
To calculate the electrical consumption of Instances, instead of using an exact measure of the power consumption, we use a proxy, e.g. CPU usage. The relationship between CPU usage and the power consumption of the underlying machine is non-linear, and characterised by a consumption profile.
63+
64+
A consumption profile is a formula that takes in a given workload (e.g. % CPU usage), and returns the estimated power consumption of the machine.
65+
66+
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.
67+
68+
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.
69+
70+
### Calculation example
71+
72+
In the example below we will calculate the manufacturing impact allocated to an Instance for an 100 hour usage period.
73+
74+
Consider the following characteristics:
75+
76+
| Resource | Instance | Hypervisor |
77+
| --- | --- | --- |
78+
| vCPU | 4 | 16 CPU cores |
79+
| RAM | 8 GB | 64 GB |
80+
| Storage | 50 GB | 1 TB (1000 GB) |
81+
| Lifespan (in years) | | 6 years = 52560h |
82+
| Manufacturing impact | | 100 kgCo2e |
83+
84+
The allocation of the hypervisor resources for this particular Instance is calculated in the following manner:
85+
86+
| Resource | Allocation |
87+
| --- | --- |
88+
| CPU | 4/16 = 0.25 |
89+
| RAM | 8/64 = 0.125 |
90+
| Storage | 50/1000 = 0.05 |
91+
| Total Instance Share | 0.25 + 0.125 + 0.05 = 0.425 |
92+
93+
We multiply the resource allocation by the Instance's lifespan ratio and the hypervisor's manufacturing impact to obtain the manufacturing impact allocated to the Instance:
94+
95+
```
96+
(100 hours / 52,680 hours) × 100 kgCO2e × 0.425 = 0.080 kgCO2eq
97+
```
98+
99+

‎pages/environmental-footprint/faq.mdx

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,16 @@ Refer to the [environmental footprint calculation breakdown](/environmental-foot
2020

2121
## Why does my environmental impact data vary over time?
2222

23-
Your environmental impact data may change due to updates in the energy mix of data center locations, adjustments to PUE, or enhancements in our calculation methodology. These updates ensure that your reports reflect the most accurate and up-to-date information, enhancing transparency and trust in our reporting system.
23+
Your environmental impact data may change due to updates in the energy mix of data center locations, adjustments to PUE, or enhancements in our calculation methodology. These updates ensure that your reports reflect the most accurate and up-to-date information, enhancing transparency and trust in our reporting system.
24+
25+
## Is hardware equipment recycled at Scaleway?
26+
27+
Scaleway is committed to responsible hardware recycling practices.
28+
29+
All equipment is thoroughly tested in our data centers and repaired whenever possible, with a notable example being the testing of over 45,000 disks in 2024, resulting in a reuse rate of nearly 30%.
30+
31+
For equipment that cannot be repaired, we partner with [Loxy](https://www.loxy.fr/about), a company specializing in the collection, recycling, and reuse of electronic waste.
32+
33+
To ensure transparency and accountability, certificates of treatment or reconditioning are obtained for each batch processed, and our approach is aligned with the European WEEE directive and the internal standards of the Iliad group.
34+
35+
Furthermore, Scaleway maintains rigorous monitoring and reporting procedures, submitting declarations to the relevant state authorities through the [Trackdéchets](https://trackdechets.beta.gouv.fr/) platform.

0 commit comments

Comments
 (0)