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
Copy file name to clipboardExpand all lines: pages/environmental-footprint/additional-content/load-balancer-env-footprint.mdx
+17-18Lines changed: 17 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,41 +28,40 @@ The total estimated environmental impact of the Load Balancer product integrates
28
28
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).
29
29
30
30
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.
35
35
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
+
<Messagetype="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>
37
39
38
40
### Usage Impact
39
41
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.
45
44
46
45
#### Calculation Example
47
46
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`
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**
64
63
65
64
<Messagetype="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).
0 commit comments