diff --git a/menu/navigation.json b/menu/navigation.json index 703fa3228a..9e5eb18777 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -274,16 +274,24 @@ { "items": [ { - "label": "Environmental Footprint calculation breakdown", + "label": "Calculation breakdown", "slug": "environmental-footprint-calculator" }, { - "label": "Environmental footprint calculator product integration", + "label": "Calculator product integration", "slug": "environmental-footprint-integration" }, { "label": "Understanding your environmental footprint estimation", "slug": "environmental-footprint-calculator-estimation" + }, + { + "label": "Bare Metal footprint calculation", + "slug": "bare-metal-env-footprint" + }, + { + "label": "Instances footprint calculation", + "slug": "instances-env-footprint" } ], "label": "Additional Content", diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-instances.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-instances.webp new file mode 100644 index 0000000000..aed0938c8f Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-instances.webp differ diff --git a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx new file mode 100644 index 0000000000..50c590e5bd --- /dev/null +++ b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx @@ -0,0 +1,54 @@ +--- +meta: + title: Bare Metal footprint calculation + description: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail. +content: + h1: Bare Metal footprint calculation + paragraph: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail. +tags: bare-metal environmental-footprint impact datacentre +dates: + validation: 2025-05-27 + posted: 2025-05-27 +categories: + - environmental-footprint + - bare-metal +--- + +At Scaleway the Bare Metal category includes different types of servers, such as: + - Apple silicon servers + - Elastic Metal servers, and + - Dedibox servers. + +This page includes the specificities of the environmental footprint calculation for Apple silicon and Elastic Metal servers. + + +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. + + +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. + +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. + + + + + 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. + + We will update our methodology as soon as more reliable data on GPU manufacturing becomes available. + + +## Calculation example + +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: + +```math +ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e +``` + +Therefore 1,62 kgCO2e is added to the total manufacturing impact of this server. + +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: + +```math +UsageFootprint = 0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e +``` \ No newline at end of file diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index 7c0cc516cc..046da2a645 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -65,10 +65,10 @@ The details of the calculations for each of these elements are detailed below. ### Definition of the variables - - All calculations will use the following variables: + + The acronyms used below are based on the French phrases for these terms. @@ -114,31 +114,16 @@ For the use of network machines induced by your use of Scaleway products, we tak 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. -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. - -#### Bare Metal +In the calculation pictured below we consider the formula for calculating the customer IT equipment impact allocation for Bare Metal servers. -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. - -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. - - - 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. - - We will update our methodology as soon as more reliable data on GPU manufacturing becomes available. - - -#### Calculation example - -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: +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. -```math -ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e -``` +You can find the calculation specifications for each of the available products in the list below: -Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server. +- [Bare Metal](/environmental-footprint/additional-content/bare-metal-env-footprint) +- [Instances](/environmental-footprint/additional-content/instances-env-footprint) ### Cross-IT equipment & stock diff --git a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx new file mode 100644 index 0000000000..796393f857 --- /dev/null +++ b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx @@ -0,0 +1,99 @@ +--- +meta: + title: Instances footprint calculation + description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. +content: + h1: Instances footprint calculation + paragraph: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. +tags: instances environmental-footprint impact cloud-computing +dates: + validation: 2025-05-27 + posted: 2025-05-27 +categories: +- environmental-footprint +- instances +--- + +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. + +## 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. + +The calculation using the elements above can be broken down into: + +### Manufacturing Impact + - Manufacturing of the underlying physical servers (hypervisors) necessary to run the Instances. + - Distribution of the manufacturing impact according to the resources consumed by the Instance (vCPU, RAM, storage). + +### Operational Impact + - Energy consumption of the hypervisors during Instance usage. + - [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts#pue-power-usage-effectiveness) specific to the data center where the Instance is hosted. + - Energy mix of the country that provides the electricity. + +### Usage Impact + - Resources consumed by the Instance, calculated based on the material specifications of the hypervisors. + +### Indirect Emissions + - Impact related to cross-functional services necessary to guarantee the operation of the Instance, such as network and shared storage. + +## Instance consumption ratio + +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. +- **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. + + + +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. + +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. + +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 calculation for Instances + +The only part of the calculation that will differ from the basis is the [Cross-IT equipment & stock calculations](/environmental-footprint/additional-content/environmental-footprint-calculator/#cross-it-equipment-and-stock). + +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. + +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. + +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](/environmental-footprint/additional-content/environmental-footprint-calculator-estimation/) of 30% CPU usage. + +### Calculation example + +In the example below we will calculate the manufacturing impact allocated to an Instance for an 100 hour usage period. + +Consider the following characteristics: + +| Resource | Instance | Hypervisor | +| --- | --- | --- | +| vCPU | 4 | 16 CPU cores | +| RAM | 8 GB | 64 GB | +| Storage | 50 GB | 1 TB (1000 GB) | +| Lifespan (in years) | | 6 years = 52560h | +| Manufacturing impact | | 100 kgCo2e | + +The allocation of the hypervisor resources for this particular Instance is calculated in the following manner: + +| Resource | Allocation | +| --- | --- | +| CPU | 4/16 = 0.25 | +| RAM | 8/64 = 0.125 | +| Storage | 50/1000 = 0.05 | +| Total Instance Share | 0.25 + 0.125 + 0.05 = 0.425 | + +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: + +``` +(100 hours / 52,680 hours) × 100 kgCO2e × 0.425 = 0.080 kgCO2eq +``` + +