From 1d6d5365aa8105ad0d2afc1a871708be3b0085ec Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 30 Oct 2025 15:21:57 +0100 Subject: [PATCH 1/6] fix(efc): lb efc --- .../load-balancer-env-footprint.mdx | 109 ++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx diff --git a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx new file mode 100644 index 0000000000..bbf2cd7c62 --- /dev/null +++ b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx @@ -0,0 +1,109 @@ +--- +title: Instances footprint calculation +description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. +tags: instances environmental-footprint impact cloud-computing +dates: + validation: 2025-10-01 + posted: 2025-05-27 +--- +import image from './assets/scaleway-allocation-rules-instances.webp' + +* Definition of the variables: We use the same variables defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#definition-of-the-variables. The Load Balancer product is based on the Instance product, therefore we take into account the impact of the underlying instances (see Instance documentation). + +* Datacenter and technical environment: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#data-center-and-technical-environment, allocated according to the underlying instances (see Instance documentation). + +* Network: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#network, allocated according to the underlying instances (see Instance documentation). + +* Customer servers: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers, allocated according to the underlying instances (see Instance documentation). + +* Cross-IT equipment & stock: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#cross-it-equipment–stock, allocated according to the underlying instances (see Instance documentation), to which we add the impact of equipment required for the load balancer's control plane. + +* Water consumption: identical to what is defined here. In the previous equations, we determined the electricity consumption associated with the use of the service; we reuse this value and multiply it by the WUE (Water Usage Effectiveness) to determine the water consumption associated with the service usage. + + +## Console overview + +Discover how to measure your footprint for Instances on the Scaleway console. + + +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](#electricity-consumption-calculation). + +### 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. + +## Electricity consumption calculation + +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. + +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. + +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 + +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 +``` From f5152b09134aa221f9112ef92563e378cb1a662f Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 10 Nov 2025 17:25:43 +0100 Subject: [PATCH 2/6] fix(efc): lb pt 2 --- .../bare-metal-env-footprint.mdx | 2 +- .../block-storage-env-footprint.mdx | 3 + .../instances-env-footprint.mdx | 4 +- .../load-balancer-env-footprint.mdx | 129 ++++++------------ .../object-storage-env-footprint.mdx | 4 + 5 files changed, 55 insertions(+), 87 deletions(-) diff --git a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx index e4fe4adad8..66fad5b493 100644 --- a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx @@ -17,7 +17,7 @@ At Scaleway the Bare Metal category includes different types of servers, such as 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. +The calculations on this page 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. diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index 35372d7d07..7a15715571 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -9,6 +9,9 @@ dates: This page includes the specificities of the environmental footprint calculation for Block Storage. + +The calculations on this page 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. + ## Calculation aspects The total estimated impact of Block Storage volumes is calculated by integrating the: diff --git a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx index cb89ff91ea..a9f01cb161 100644 --- a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx @@ -14,7 +14,9 @@ import image from './assets/scaleway-allocation-rules-instances.webp' Discover how to measure your footprint for Instances on the Scaleway console. -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. + +The calculations on this page 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. + ## Calculation aspects diff --git a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx index bbf2cd7c62..46caeb58fc 100644 --- a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx @@ -1,109 +1,68 @@ --- -title: Instances footprint calculation -description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. -tags: instances environmental-footprint impact cloud-computing +title: Load Balancer Footprint Calculation +description: This page explains how Scaleway calculates the environmental footprint of its Load Balancer product in detail. +tags: load-balancer environmental-footprint impact networking dates: - validation: 2025-10-01 - posted: 2025-05-27 + validation: 2025-11-10 + posted: 2025-11-10 --- -import image from './assets/scaleway-allocation-rules-instances.webp' -* Definition of the variables: We use the same variables defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#definition-of-the-variables. The Load Balancer product is based on the Instance product, therefore we take into account the impact of the underlying instances (see Instance documentation). +Scaleway Load Balancers are built on top of the Instances infrastructure, meaning their environmental footprint is derived from the underlying virtual instances that power the service. The footprint calculation also accounts for additional control plane components specific to the Load Balancer service. -* Datacenter and technical environment: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#data-center-and-technical-environment, allocated according to the underlying instances (see Instance documentation). +This page details how the environmental impact of Load Balancers is calculated. -* Network: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#network, allocated according to the underlying instances (see Instance documentation). + +The calculations described on this page take into consideration all the elements described in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/) documentation page. + -* Customer servers: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers, allocated according to the underlying instances (see Instance documentation). +## Calculation Aspects -* Cross-IT equipment & stock: We perform the same calculation as defined here https://www.scaleway.com/en/docs/environmental-footprint/additional-content/environmental-footprint-calculator/#cross-it-equipment–stock, allocated according to the underlying instances (see Instance documentation), to which we add the impact of equipment required for the load balancer's control plane. +The total estimated environmental impact of the Load Balancer product integrates the following components: -* Water consumption: identical to what is defined here. In the previous equations, we determined the electricity consumption associated with the use of the service; we reuse this value and multiply it by the WUE (Water Usage Effectiveness) to determine the water consumption associated with the service usage. +- **Dedicated manufacturing impact** – Related to the physical servers hosting the virtual instances that run the Load Balancer service. +- **Related manufacturing impact** – Includes the impact of tools used to manage the service: control plane, monitoring systems, and internal networking infrastructure. +- **Energy usage impact** – The average electricity consumption during operation, including associated data center infrastructure (PUE), network, and cross-IT equipment. +### Allocation Methodology -## Console overview +The Load Balancer product reuses the same environmental footprint model as [Instances](/environmental-footprint/additional-content/instances-env-footprint/), with impact allocated based on the underlying instance usage. All variables (e.g., server lifespan, energy mix, PUE) follow the definitions established in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/#definition-of-the-variables). -Discover how to measure your footprint for Instances on the Scaleway console. - +Specifically: +- **Datacenter and technical environment**: Calculated as defined in the mother page, allocated according to the underlying instances [environmental-footprint-calculator.mdx]. +- **Network impact**: Allocated proportionally based on the underlying instances’ network usage [environmental-footprint-calculator.mdx]. +- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage [environmental-footprint-calculator.mdx]. +- **Cross-IT equipment & stock**: The base calculation follows the general methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane. -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. +> The manufacturing and energy impacts are first computed at the instance level, then attributed to Load Balancer usage based on resource consumption share. ### Usage Impact - - Resources consumed by the Instance, [calculated based on the material specifications of the hypervisors](#electricity-consumption-calculation). - -### 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. +The energy consumption of Load Balancers is derived from the underlying instances. We use CPU usage as a proxy, applying [Boavizta’s non-linear consumption profiles](https://doc.api.boavizta.org/Reference/routes/#consumption-profile-routes) to estimate power draw. -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. +For operational impact: +- **Energy mix**: French grid emission factor: 0.065 kgCO2e/kWh +- **PUE**: 1.16 (average across Scaleway data centers) -## Electricity consumption calculation +#### Calculation Example -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. +Assume a Load Balancer runs on an underlying instance with: +- Power consumption: 110 W (0.110 kW) +- Usage duration: 100 hours +- Allocation ratio (based on instance share): `lb_ratio = 0.5` -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. - -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 - -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 | +**Energy Usage Impact**: +```math +UsageFootprint = 0.110 \times 100 \times 0.065 \times 1.16 = 0.825\ kgCO2e +``` -The allocation of the hypervisor resources for this particular Instance is calculated in the following manner: +**Manufacturing Impact** (6-year lifespan = 52,560 hours, manufacturing impact = 850 kgCO2e): +```math +ManufacturingImpact = (100 / 52560) \times 850 \times 0.5 = 0.81\ kgCO2e +``` -| 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 | +Total footprint: **1.635 kgCO2e** for 100 hours of usage. -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: + +Water consumption is derived from the same energy usage value, multiplied by the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness) of the data center. This applies to zones where WUE data is available (FR-PAR-1, FR-PAR-2, FR-PAR-3, NL-AMS-1) [environmental-footprint-calculator.mdx]. + -``` -(100 hours / 52,680 hours) * 100 kgCO2e * 0.425 = 0.080 kgCO2eq -``` diff --git a/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx index 8e86525407..0d59cdd2ac 100644 --- a/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx @@ -10,6 +10,10 @@ dates: This page includes the specificities of the environmental footprint calculation for Object Storage. + +The calculations on this page 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. + + ## Calculation aspects The total estimated impact of Object Storage volumes is calculated by integrating the: From 127f1dc61baa9fce3b47a8cb9467a0035d64fe66 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 10 Nov 2025 17:43:37 +0100 Subject: [PATCH 3/6] fix(efc): lb pt4 --- .../load-balancer-env-footprint.mdx | 35 +++++++++---------- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx index 46caeb58fc..28f4ac1dec 100644 --- a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx @@ -28,41 +28,40 @@ The total estimated environmental impact of the Load Balancer product integrates The Load Balancer product reuses the same environmental footprint model as [Instances](/environmental-footprint/additional-content/instances-env-footprint/), with impact allocated based on the underlying instance usage. All variables (e.g., server lifespan, energy mix, PUE) follow the definitions established in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/#definition-of-the-variables). Specifically: -- **Datacenter and technical environment**: Calculated as defined in the mother page, allocated according to the underlying instances [environmental-footprint-calculator.mdx]. -- **Network impact**: Allocated proportionally based on the underlying instances’ network usage [environmental-footprint-calculator.mdx]. -- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage [environmental-footprint-calculator.mdx]. -- **Cross-IT equipment & stock**: The base calculation follows the general methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane. +- **Datacenter and technical environment**: are calculated as defined in the global calculation methodology, and allocated according to the underlying instances. +- **Network impact**: Allocated proportionally based on the underlying instances’ network usage. +- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage. +- **Cross-IT equipment & stock**: The base calculation follows the global methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane. -> The manufacturing and energy impacts are first computed at the instance level, then attributed to Load Balancer usage based on resource consumption share. + +The manufacturing and energy impacts are first computed at the Instance level, then attributed to Load Balancer usage based on resource consumption share. + ### Usage Impact -The energy consumption of Load Balancers is derived from the underlying instances. We use CPU usage as a proxy, applying [Boavizta’s non-linear consumption profiles](https://doc.api.boavizta.org/Reference/routes/#consumption-profile-routes) to estimate power draw. - -For operational impact: -- **Energy mix**: French grid emission factor: 0.065 kgCO2e/kWh -- **PUE**: 1.16 (average across Scaleway data centers) +- The energy consumption of Load Balancers is derived from the underlying instances. We use CPU usage as a proxy, applying [Boavizta’s consumption profiles](https://doc.api.boavizta.org/Reference/routes/#consumption-profile-routes) to estimate power draw. +- The operational environmental impact of a service depends on two key factors: the **energy mix** of the host country and the datacenter's **PUE**. Refer to the [Calculation reference values](/environmental-footprint/additional-content/calculation-values-reference) documentation page to find the values corresponding to your region. #### Calculation Example -Assume a Load Balancer runs on an underlying instance with: -- Power consumption: 110 W (0.110 kW) -- Usage duration: 100 hours -- Allocation ratio (based on instance share): `lb_ratio = 0.5` +Assume a Load Balancer runs on an underlying Instance with: +- **Power consumption:** 110 W (0.110 kW) +- **Usage duration:** 100 hours +- **Allocation ratio** (based on instance share): `lb_ratio = 0.5` **Energy Usage Impact**: ```math -UsageFootprint = 0.110 \times 100 \times 0.065 \times 1.16 = 0.825\ kgCO2e +UsageFootprint = 0.110 * 100 * 0.065 * 1.16 = 0.825 kgCO2e ``` **Manufacturing Impact** (6-year lifespan = 52,560 hours, manufacturing impact = 850 kgCO2e): ```math -ManufacturingImpact = (100 / 52560) \times 850 \times 0.5 = 0.81\ kgCO2e +ManufacturingImpact = (100 / 52560) * 850 * 0.5 = 0.81 kgCO2e ``` -Total footprint: **1.635 kgCO2e** for 100 hours of usage. +This means that the total footprint for 100 hours of Load Balancer usage, in this case, is **1.635 kgCO2e** -Water consumption is derived from the same energy usage value, multiplied by the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness) of the data center. This applies to zones where WUE data is available (FR-PAR-1, FR-PAR-2, FR-PAR-3, NL-AMS-1) [environmental-footprint-calculator.mdx]. +Water consumption is derived from the same energy usage value, multiplied by the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness) of the datacenter. This applies to zones where WUE data is available (FR-PAR-1, FR-PAR-2, FR-PAR-3, NL-AMS-1). From 5f7ada2bcadbcae11beb1fdcef8c447d7c22cb01 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 10 Nov 2025 17:51:51 +0100 Subject: [PATCH 4/6] fix(efc): lb pt5 --- pages/environmental-footprint/menu.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/environmental-footprint/menu.ts b/pages/environmental-footprint/menu.ts index 3c5c5f3ffe..c35a8382a6 100644 --- a/pages/environmental-footprint/menu.ts +++ b/pages/environmental-footprint/menu.ts @@ -56,6 +56,10 @@ export const environmentalFootprintMenu = { { label: 'Object Storage footprint calculation', slug: 'object-storage-env-footprint' + }, + { + label: 'Load Balancer footprint calculation', + slug: 'load-balancer-env-footprint' } ], label: 'Additional Content', From 1e922980326684751affe65120d1649a21379978 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 1 Dec 2025 16:21:21 +0100 Subject: [PATCH 5/6] fix(efc): review elise pt1 Co-authored-by: eauvray-github <67907289+eauvray-github@users.noreply.github.com> --- .../additional-content/load-balancer-env-footprint.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx index 28f4ac1dec..0c98a8db7d 100644 --- a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx @@ -30,7 +30,7 @@ The Load Balancer product reuses the same environmental footprint model as [Inst Specifically: - **Datacenter and technical environment**: are calculated as defined in the global calculation methodology, and allocated according to the underlying instances. - **Network impact**: Allocated proportionally based on the underlying instances’ network usage. -- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage. +- **Customer servers**: Impact is calculated using the same method as for [Instances](/environmental-footprint/additional-content/instances-env-footprint/), and allocated according to instance usage. - **Cross-IT equipment & stock**: The base calculation follows the global methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane. @@ -47,7 +47,6 @@ The manufacturing and energy impacts are first computed at the Instance level, t Assume a Load Balancer runs on an underlying Instance with: - **Power consumption:** 110 W (0.110 kW) - **Usage duration:** 100 hours -- **Allocation ratio** (based on instance share): `lb_ratio = 0.5` **Energy Usage Impact**: ```math From 2cdb37bce697942dc2424958aa9b15129db64ae6 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 1 Dec 2025 16:26:15 +0100 Subject: [PATCH 6/6] fix(efc): review elise pt2 --- .../additional-content/load-balancer-env-footprint.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx index 0c98a8db7d..827cb57a0c 100644 --- a/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx @@ -47,13 +47,16 @@ The manufacturing and energy impacts are first computed at the Instance level, t Assume a Load Balancer runs on an underlying Instance with: - **Power consumption:** 110 W (0.110 kW) - **Usage duration:** 100 hours +- **French energy mix:** O,065kgCo2e/kwh +- **Datacenter's PUE:** 1,16 **Energy Usage Impact**: ```math UsageFootprint = 0.110 * 100 * 0.065 * 1.16 = 0.825 kgCO2e ``` -**Manufacturing Impact** (6-year lifespan = 52,560 hours, manufacturing impact = 850 kgCO2e): +**Manufacturing Impact** (6-year lifespan = 52,560 hours, example manufacturing impact = 850 kgCO2e): + ```math ManufacturingImpact = (100 / 52560) * 850 * 0.5 = 0.81 kgCO2e ```