Skip to content

Commit 127f1dc

Browse files
fix(efc): lb pt4
1 parent f5152b0 commit 127f1dc

File tree

1 file changed

+17
-18
lines changed

1 file changed

+17
-18
lines changed

pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -28,41 +28,40 @@ The total estimated environmental impact of the Load Balancer product integrates
2828
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).
2929

3030
Specifically:
31-
- **Datacenter and technical environment**: Calculated as defined in the mother page, allocated according to the underlying instances [environmental-footprint-calculator.mdx].
32-
- **Network impact**: Allocated proportionally based on the underlying instances’ network usage [environmental-footprint-calculator.mdx].
33-
- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage [environmental-footprint-calculator.mdx].
34-
- **Cross-IT equipment & stock**: The base calculation follows the general methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane.
31+
- **Datacenter and technical environment**: are calculated as defined in the global calculation methodology, and allocated according to the underlying instances.
32+
- **Network impact**: Allocated proportionally based on the underlying instances’ network usage.
33+
- **Customer servers**: Impact is calculated using the same method as for Bare Metal servers, but allocated according to instance usage.
34+
- **Cross-IT equipment & stock**: The base calculation follows the global methodology, with an **additional allocation** for equipment dedicated to the Load Balancer control plane.
3535

36-
> The manufacturing and energy impacts are first computed at the instance level, then attributed to Load Balancer usage based on resource consumption share.
36+
<Message type="note">
37+
The manufacturing and energy impacts are first computed at the Instance level, then attributed to Load Balancer usage based on resource consumption share.
38+
</Message>
3739

3840
### Usage Impact
3941

40-
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.
41-
42-
For operational impact:
43-
- **Energy mix**: French grid emission factor: 0.065 kgCO2e/kWh
44-
- **PUE**: 1.16 (average across Scaleway data centers)
42+
- 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.
43+
- 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.
4544

4645
#### Calculation Example
4746

48-
Assume a Load Balancer runs on an underlying instance with:
49-
- Power consumption: 110 W (0.110 kW)
50-
- Usage duration: 100 hours
51-
- Allocation ratio (based on instance share): `lb_ratio = 0.5`
47+
Assume a Load Balancer runs on an underlying Instance with:
48+
- **Power consumption:** 110 W (0.110 kW)
49+
- **Usage duration:** 100 hours
50+
- **Allocation ratio** (based on instance share): `lb_ratio = 0.5`
5251

5352
**Energy Usage Impact**:
5453
```math
55-
UsageFootprint = 0.110 \times 100 \times 0.065 \times 1.16 = 0.825\ kgCO2e
54+
UsageFootprint = 0.110 * 100 * 0.065 * 1.16 = 0.825 kgCO2e
5655
```
5756

5857
**Manufacturing Impact** (6-year lifespan = 52,560 hours, manufacturing impact = 850 kgCO2e):
5958
```math
60-
ManufacturingImpact = (100 / 52560) \times 850 \times 0.5 = 0.81\ kgCO2e
59+
ManufacturingImpact = (100 / 52560) * 850 * 0.5 = 0.81 kgCO2e
6160
```
6261

63-
Total footprint: **1.635 kgCO2e** for 100 hours of usage.
62+
This means that the total footprint for 100 hours of Load Balancer usage, in this case, is **1.635 kgCO2e**
6463

6564
<Message type="important">
66-
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].
65+
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).
6766
</Message>
6867

0 commit comments

Comments
 (0)