-
Notifications
You must be signed in to change notification settings - Fork 258
feat(efc): load balancer - MTA-6653 #5783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| --- | ||
| 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-11-10 | ||
| posted: 2025-11-10 | ||
| --- | ||
|
|
||
| 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. | ||
|
|
||
| This page details how the environmental impact of Load Balancers is calculated. | ||
|
|
||
| <Message type="important"> | ||
| 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. | ||
| </Message> | ||
|
|
||
| ## Calculation Aspects | ||
|
|
||
| The total estimated environmental impact of the Load Balancer product integrates the following components: | ||
|
|
||
| - **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 | ||
|
|
||
| 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**: 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. | ||
|
|
||
| <Message type="note"> | ||
| The manufacturing and energy impacts are first computed at the Instance level, then attributed to Load Balancer usage based on resource consumption share. | ||
| </Message> | ||
|
|
||
| ### Usage Impact | ||
|
|
||
| - 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` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. En réalité pour load balancer il n'y a pas "d'allocation ratio", un lb utilise une instance donc on peut supprimer cette ligne |
||
|
|
||
| **Energy Usage Impact**: | ||
| ```math | ||
| UsageFootprint = 0.110 * 100 * 0.065 * 1.16 = 0.825 kgCO2e | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. je rajouterai le 0,065 et le 1,16 dans la liste des valeurs mentionné au dessus afin que ce soit plus claire. Il faudra indiquer que ce sont des valeurs fictive, a titre d'exemple, comme ca si les vrai valeur évoluent, on n'aura pas besoin de modifier ici |
||
| ``` | ||
|
|
||
| **Manufacturing Impact** (6-year lifespan = 52,560 hours, manufacturing impact = 850 kgCO2e): | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. je préciserai que le manufacturing impact de 850kg est une valeur fictive a titre d'exemple |
||
| ```math | ||
| ManufacturingImpact = (100 / 52560) * 850 * 0.5 = 0.81 kgCO2e | ||
| ``` | ||
|
|
||
| This means that the total footprint for 100 hours of Load Balancer usage, in this case, is **1.635 kgCO2e** | ||
|
|
||
| <Message type="important"> | ||
| 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). | ||
| </Message> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.