You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
21
+
22
+
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.
23
+
24
+
<Messagetype="important">
25
+
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.
26
+
27
+
We will update our methodology as soon as more reliable data on GPU manufacturing becomes available.
28
+
</Message>
29
+
30
+
##### Calculation example
31
+
32
+
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:
The acronyms used below are based on the French phrases for these terms.
74
74
</Message>
@@ -118,101 +118,6 @@ Each product will have its own set of criteria to allocate the environmental foo
118
118
119
119
You can find the calculation specifications for each of the available products in the list below. Click on a product name to expand or collapse its details.
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.
127
-
128
-
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.
129
-
130
-
<Messagetype="important">
131
-
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.
132
-
133
-
We will update our methodology as soon as more reliable data on GPU manufacturing becomes available.
134
-
</Message>
135
-
136
-
##### Calculation example
137
-
138
-
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:
Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server.
145
-
</Concept>
146
-
147
-
<Concept>
148
-
#### Instances
149
-
150
-
For Instances, the calculation of the environmental footprint takes into consideration all the elements already described on this page.
151
-
152
-
The calculations performed across all phases of the product lifecycle are considered, including the calculations for Bare Metal, as Instances are hosted on physical servers.
153
-
154
-
The following elements are additionally considered:
155
-
- **Hypervisor resources** - the resources (CPU, RAM, and disk, for example) used in the physical hypervisor servers that create and run the virtual Instances.
156
-
- **Instance offer resources** - the vCPU, RAM, and disk resources used when you use an Instance.
157
-
158
-
The calculation for the elements above can be broken down into:
159
-
- **Manufacturing Impact**
160
-
- Manufacturing of the underlying physical servers (hypervisors) necessary to run the Instances.
161
-
- Distribution of the manufacturing impact according to the resources consumed by the Instance (vCPU, RAM, storage).
162
-
- **Operational Impact**
163
-
- Energy consumption of the hypervisors during Instance usage.
164
-
- [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts#pue-power-usage-effectiveness) specific to the data center where the Instance is hosted.
165
-
- Energy mix of the country that provides the electricity.
166
-
- **Usage Impact**
167
-
- Resources consumed by the Instance, calculated based on the material specifications of the hypervisors.
168
-
- **Indirect Emissions**
169
-
- Impact related to cross-functional services necessary to guarantee the operation of the Instance, such as network and shared storage.
170
-
171
-
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.
172
-
173
-
-**CPU** - Consider the share of vCPUs reserved compared to the total number of physical cores available.
174
-
-**RAM** - Consider the share of allocated RAM compared to the total RAM of the hypervisor.
175
-
-**Storage** - Consider the use of allocated storage compared to the total capacity of the hypervisor.
To calculate the Instance's energy consumption we:
199
-
200
-
1. Consider the hypervisor's consumption (1000 kWh) and multiply it by the total Instance share (0.425):
201
-
```
202
-
1000 kWh × 0.425 = 425 kWh
203
-
```
204
-
2. Adjust the energy consumption based on the [PUE](/environmental-footprint/concepts#pue-power-usage-effectiveness) of the data center (1.3) where the hypervisor is located:
205
-
```
206
-
425 kWh × 1.3 = 552.5 kWh
207
-
```
208
-
3. Calculate the total emissions of the Instance based on the energy mix (300 gCO2eq/kWh) of the country where the hypervisor is located:
@@ -237,7 +142,7 @@ To integrate this into the overall calculation, we will first get the total envi
237
142
238
143
Providing water consumption metrics is essential in the context of cloud services hosted in data centers because water plays a key role in cooling systems, which ensure the optimal operating temperatures for servers. The amount of water consumed depends on factors such as the temperature, humidity, and the design of the cooling system. For instance, in hot and dry climates, water consumption tends to be higher. At Scaleway, we choose our data centers also taking this criterion into account to reduce water consumption as much as possible.
For 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.
17
+
18
+
The calculations performed across all phases of the product lifecycle are considered, including the calculations for Bare Metal, as Instances are hosted on physical servers.
19
+
20
+
The following elements are additionally considered:
21
+
-**Hypervisor resources** - the resources (CPU, RAM, and disk, for example) used in the physical hypervisor servers that create and run the virtual Instances.
22
+
-**Instance offer resources** - the vCPU, RAM, and disk resources used when you use an Instance.
23
+
24
+
The calculation for the elements above can be broken down into:
25
+
26
+
## Calculation aspects
27
+
28
+
### Manufacturing Impact
29
+
- Manufacturing of the underlying physical servers (hypervisors) necessary to run the Instances.
30
+
- Distribution of the manufacturing impact according to the resources consumed by the Instance (vCPU, RAM, storage).
31
+
32
+
### Operational Impact
33
+
- Energy consumption of the hypervisors during Instance usage.
34
+
- [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts#pue-power-usage-effectiveness) specific to the data center where the Instance is hosted.
35
+
- Energy mix of the country that provides the electricity.
36
+
37
+
### Usage Impact
38
+
- Resources consumed by the Instance, calculated based on the material specifications of the hypervisors.
39
+
40
+
41
+
### Indirect Emissions
42
+
- Impact related to cross-functional services necessary to guarantee the operation of the Instance, such as network and shared storage.
43
+
44
+
45
+
46
+
## Instance consumption ratio
47
+
48
+
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.
49
+
50
+
-**CPU** - Consider the share of vCPUs reserved compared to the total number of physical cores available.
51
+
-**RAM** - Consider the share of allocated RAM compared to the total RAM of the hypervisor.
52
+
-**Storage** - Consider the use of allocated storage compared to the total capacity of the hypervisor.
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. From now on we will refer to the Instance consumption ratio as `Resources_Used_VM`.
57
+
58
+
Refer to the table below to understand how the `Resources_Used_VM` is integrated into the calculation of each aspect of the total fooprint calculation.
59
+
60
+
| Calculation aspect | Formula |
61
+
| --- | --- |
62
+
| Datacenter Manufacturing Impact | (Du_vm / DDV_dc) x (Puiss_vm / Puiss_DC) x EF_dc x Resources_Used_VM |
63
+
| Network Equipment Manufacturing Impact | (Du_vm / DDV_reseau) x (Puiss_vm / Puiss_reseau) x EF_reseau x Resources_Used_VM|
64
+
| Internal Infrastructure Manufacturing and Usage Impact | (Du_vm / DDV_infra) x (Puiss_vm / Puiss_infra) x EF_infra x Resources_Used_VM |
65
+
| Instance Infrastructure Manufacturing and Usage Impact | DIFFERENTTTTTTTTTTTTROEIHOIHOTRIH|
66
+
| Equipment in Stock Manufacturing and Usage Impact | (Du_vm / DDV_stock) x (Puiss_vm / Puiss_stock) x EF_stock x Resources_Used_VM |
67
+
68
+
69
+
## Calculation example
70
+
71
+
In this example we will calculate the impact of an Instance with the following characteristics:
72
+
73
+
| Resource | VM | Hypervisor |
74
+
| --- | --- | --- |
75
+
| vCPU | 4 | 16 CPU cores |
76
+
| RAM | 8 GB | 64 GB |
77
+
| Storage | 50 GB | 1 TB (1000 GB) |
78
+
79
+
The allocation of the hypervisor resources for this particular Instance is calculated in the following manner:
To calculate the Instance's energy consumption we:
89
+
90
+
1. Consider the hypervisor's consumption (1000 kWh) and multiply it by the total Instance share (0.425):
91
+
```
92
+
1000 kWh × 0.425 = 425 kWh
93
+
```
94
+
2. Adjust the energy consumption based on the [PUE](/environmental-footprint/concepts#pue-power-usage-effectiveness) of the data center (1.3) where the hypervisor is located:
95
+
```
96
+
425 kWh × 1.3 = 552.5 kWh
97
+
```
98
+
3. Calculate the total emissions of the Instance based on the energy mix (300 gCO2eq/kWh) of the country where the hypervisor is located:
0 commit comments