[irtf-discuss] Re: [E-impact] Re: [Green] Network Equipment Energy Efficiency Metric

Hesham ElBakoury <helbakoury@gmail.com> Thu, 14 November 2024 12:14 UTC

Return-Path: <helbakoury@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46342C15152D for <irtf-discuss@ietfa.amsl.com>; Thu, 14 Nov 2024 04:14:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XONLP22RQdhb for <irtf-discuss@ietfa.amsl.com>; Thu, 14 Nov 2024 04:14:55 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D588C14F69A for <irtf-discuss@irtf.org>; Thu, 14 Nov 2024 04:14:55 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id 98e67ed59e1d1-2e2a999b287so482063a91.0 for <irtf-discuss@irtf.org>; Thu, 14 Nov 2024 04:14:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731586494; x=1732191294; darn=irtf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Gx3JL9bNuuQqJflPwGrOW8fxMBtpUz9oZ0i3QMVCVV0=; b=DnEgTsh8/HsOkoQDL7AV+iF/vEUoU0vRxVy7lFSbkZRHj8nLEZ/pJP9EH9bPrKMbrm 4iQsOsDfPfdQBND2Dn5JK/Wk/lTSLURfWJbMHEzNjzJ9HO4TlZxR8NiqfRdqnbAXTvyo qBFEqZo2HwHfMN1rYYOy9hVyYor4HmH+oe20s9vVw/3azrFZmKJKhsOmk9XN7Ln63vFZ IGTvYHNL1ZCRkZse38JE8JBBQzDDgrNImdQ3z8i1lgboq+koXKeXooH59NGJZ+T7rFzw XL7Sz+CEtO3InC8+SYxGhokQ0T7MhEmfFR152qFRtnA3dmQBWvTNfQgWNh8Pe8LZ8WdV +vig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731586494; x=1732191294; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Gx3JL9bNuuQqJflPwGrOW8fxMBtpUz9oZ0i3QMVCVV0=; b=nD0DOMz/RLWRgs/qWffQC4UwgSMjctMPDS+jprptbSXhiTZPMpeIR2opC0TXI8mVxd Od0ra3/PqBk9D3/zxW0x5iE+1nL1gzgS2STJxtKFZadGVYPtSatEA9r3eGNWHbVpTjpx fJkv49vE1/xGKQkwU4VDpe6HihirLhNLctJrCexBdgEUz1/LRFJRu0ovJf0XffuZmpHB Cn4nbj4R61qedhFSxGc955EH++dqRufhcgw6lyuRpV5Lo/HSdXw6wVQnFjG5aU4BUf1S wbrwjThOsRxO0h9sqDkTL0qHoDKYAVkWqGg9wwYlVG1f2C3vYq0jrvhfhnNu2Vxht6YV XZuA==
X-Forwarded-Encrypted: i=1; AJvYcCXHBLB+x18UfHEFFFgaK03qj61SIEGpUa6rHQYOXYIzDDRkcKZl0gDiqcwnY5yZ7g9N5pSFTJpNoA43OfM=@irtf.org
X-Gm-Message-State: AOJu0YwKg+TvGZu1UsHcYeYEB+zlx9cyqAOXPbYqqJd52ssBSReX/1yy iF6YV4nWws+kkbV7A4GJJbb40dTRr9hYQX4ASXd6uA1iJzglEs7d+n7rtS+6IJ869EnPWI1HtjI K13SuoQ7xrz5VHvi0JO/D3y4ICpY=
X-Google-Smtp-Source: AGHT+IG8ZC/LlfaEuoJB7SFECBd2W5jRfKymqVLL8N39F2kAQy9fohccscKSk9YM+6O0Sapu9myRSKtGUS5mgLEGH0w=
X-Received: by 2002:a17:90b:4acb:b0:2e2:ddfa:24d5 with SMTP id 98e67ed59e1d1-2e9f2c78504mr8816109a91.15.1731586494288; Thu, 14 Nov 2024 04:14:54 -0800 (PST)
MIME-Version: 1.0
References: <CAFvDQ9ruuSkrxU4wQz21Ldfp4T4s2MnojJ3H9TFBHdBsQdZm5w@mail.gmail.com> <361466.1731421949@dyas> <LO2P123MB4634D0A59EB238D2BFD8E9E19F592@LO2P123MB4634.GBRP123.PROD.OUTLOOK.COM> <DCB3A12B-3F46-4782-A9B7-19363B247F74@gmail.com> <CWLP123MB46267CADC557DE2A5DE89F8C9F592@CWLP123MB4626.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <CWLP123MB46267CADC557DE2A5DE89F8C9F592@CWLP123MB4626.GBRP123.PROD.OUTLOOK.COM>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Thu, 14 Nov 2024 04:14:42 -0800
Message-ID: <CAFvDQ9rFsHMVvPp2_7i3zAdhNEus9yrA9AvR3Wn5491vVUw8=Q@mail.gmail.com>
To: Mark Butcher <mark@posetiv.co.uk>
Content-Type: multipart/alternative; boundary="000000000000e3dc050626de65a5"
Message-ID-Hash: O2YU3LAM5ZEOBJCGIK2XI7G6G4NC3P3G
X-Message-ID-Hash: O2YU3LAM5ZEOBJCGIK2XI7G6G4NC3P3G
X-MailFrom: helbakoury@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-irtf-discuss.irtf.org-0; header-match-irtf-discuss.irtf.org-1; header-match-irtf-discuss.irtf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Dean Bogdanovic <ivandean@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, green@ietf.org, E-Impact IETF <e-impact@ietf.org>, irtf-discuss@irtf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [irtf-discuss] Re: [E-impact] Re: [Green] Network Equipment Energy Efficiency Metric
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/WlZF2Err7-e0kYe7QG_TGvyezaY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Owner: <mailto:irtf-discuss-owner@irtf.org>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Subscribe: <mailto:irtf-discuss-join@irtf.org>
List-Unsubscribe: <mailto:irtf-discuss-leave@irtf.org>

Hi Mark,
Did you look at SCI (Software Carbon Intensity) metric which is developed
by Green Software Foundation and standardized by ISO [1]. It  can be
defined for any unit including a user.

The equation to calculate an SCI score is elegantly simple. This simplicity
means it can be applied in a number of different scenarios.

[image: alt_text]

SCI = ((E *I) + M) per R

E = Energy consumed by a software system I = Location-based marginal carbon
emissions*M = Embodied emissions of a software system.* R = Functional unit
(e.g. carbon per additional user, API-call, ML job, etc)

I am wondering who is using it?
Hesham
[1]
https://learn.greensoftware.foundation/measurement/#:~:text=The%20Software%20Carbon%20Intensity%20(SCI)%20specification%20is%20a%20methodology%20developed,cars%20they%20produce%20every%20year
.

On Tue, Nov 12, 2024, 10:27 AM Mark Butcher <mark@posetiv.co.uk> wrote:

> Hello!
>
>
>
> I’m definitely never going to claim to be a grid expert, but…
> understanding the grid’s dynamics, especially active, reactive, and
> apparent power is definitely essential if the objective is to get a better
> handle on power usage across networks. It’s obvs. not just about energy
> efficiency; translating this into carbon emissions gets even more critical
> when you consider how different power sources impact the grid's overall
> carbon intensity. I’ve had some interesting chats with operators this year
> around how they are planning to move from supply side to demand side
> shaping.
>
>
>
> I don’t envy the Grid operators facing the balancing act between cost,
> stability, emissions targets, and resilience (especially as the subject of
> renewables come into play). Getting even vaguely accurate carbon intensity
> metrics from them isn’t easy and there’s lot of sweeping assumptions.
> What’s your view on the regional info shared by operators like the National
> Grid? I don’t think it’s perfect but it’s at least more accurate than a
> national average as it reflects their understanding of the flows/mix.
>
>
>
> Starting with simpler elements, like SFPs, and then scaling up to more
> complex topologies makes sense. Tracking energy consumption at this
> granular level, from individual components up to entire network sections,
> could provide the data points needed to make informed decisions on reducing
> emissions, rather than just measuring usage (if we assume we can use
> intensity metrics from the operators).
>
>
>
> Do you think breaking it down into energy consumption at the element,
> group, and network levels would give insights we could actually use and
> more importantly to act on? Or is this overkill without an agreed
> structure/approach on what to do with the data and how to interpret it?
>
>
>
> Have you got any good examples where you’ve seen this work? I’m doing a
> lot of work in data centres on this subject and the networks teams are
> often excluded because of the complexity of their operations (outside of
> core DC networks).
>
>
>
> Looking forward to discussing this further! I personally believe there’s
> definitely a lot we can do. It would also be good to consider how the data
> that’s collated can be rolled into the reporting within IT and the wider
> business.
>
>
>
> Thanks
>
>
>
> Mark
>
>
>
>
>
>
>
> *From: *Dean Bogdanovic <ivandean@gmail.com>
> *Date: *Tuesday, 12 November 2024 at 17:20
> *To: *Mark Butcher <mark@posetiv.co.uk>
> *Cc: *Michael Richardson <mcr+ietf@sandelman.ca>, green@ietf.org <
> green@ietf.org>, E-Impact IETF <e-impact@ietf.org>, irtf-discuss@irtf.org
> <irtf-discuss@irtf.org>
> *Subject: *Re: [Green] [E-impact] Network Equipment Energy Efficiency
> Metric
>
> I’m really curious how many people understand how electrical grid operates,
>
> the difference between active, reactive and apparent power in electrical
> grid. And how the grip operators are balancing power plants to maintain the
> needed power levels, how the operators decide between economic dispatch,
> grid stability and frequency regulation, environmental regulations and
> emissions , operational flexibility at the power plants etc.
> Until we do, I would not speak about CO2 emissions and other complex
> energy and traffic engineering relations.
>
> Lets first figure out how to report energy consumption by the networks,
> from very basic power consumers (SFPs) to more complex, like topologies.
> And provide the ability to provide the energy consumption information about
> an element, group of elements, part of network or even whole network to
> people who will know what to do with the info.
>
> Dean
>
> On 12 Nov 2024, at 14:59, Mark Butcher wrote:
>
> What’s interesting is seeing how kWh/GB is so variable – either based on
> network demand, the reality of the power curve and most importantly for me,
> when translated into CO2e how the variability massively increases (time and
> location)
>
>
>
>
>
> *From:* Michael Richardson <mcr+ietf@sandelman.ca>
> *Date:* Tuesday, 12 November 2024 at 14:32
> *To:* green@ietf.org <green@ietf.org>, E-Impact IETF <e-impact@ietf.org>,
> irtf-discuss@irtf.org <irtf-discuss@irtf.org>
> *Subject:* [Green] Re: [E-impact] Network Equipment Energy Efficiency
> Metric
>
>
> Is is useful for network planners to know kWh/peak-GB for an entire
> infrastructure?
>
> This doesn't try to model reaction of network equipment to increased flows,
> but rather to model how infrastructure grows to accomodate higher peak
> loads?
>
> There is also an induced demand issue.  Networks grow when they fill,
> assuming there is revenue to support it.  This is akin to transportation:
>       https://www.vtpi.org/gentraf.pdf
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*
>
> _______________________________________________
> Green mailing list -- green@ietf.org
> To unsubscribe send an email to green-leave@ietf.org
>
> --
> E-impact mailing list -- e-impact@ietf.org
> To unsubscribe send an email to e-impact-leave@ietf.org
>