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

Tony Li <tony.li@tony.li> Tue, 12 November 2024 18:40 UTC

Return-Path: <tony1athome@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 B8D9AC1ECA7A for <irtf-discuss@ietfa.amsl.com>; Tue, 12 Nov 2024 10:40:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.755
X-Spam-Level:
X-Spam-Status: No, score=-1.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 YpPh9BOgVDAD for <irtf-discuss@ietfa.amsl.com>; Tue, 12 Nov 2024 10:40:23 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 ED9E9C20C8E0 for <irtf-discuss@irtf.org>; Tue, 12 Nov 2024 10:40:23 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-20cd76c513cso51370825ad.3 for <irtf-discuss@irtf.org>; Tue, 12 Nov 2024 10:40:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731436823; x=1732041623; darn=irtf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=VrmzWQrcfubT1wVvphopmQXKMuGUBxYX3etJgjkUDYw=; b=ZTRcDCmgPGNb0RTh0CzPhPUOGYFyKkrDbyh/dw90udEoje0Ggx9X26wQ3O8DB3Kpo8 MVSY836unAvjNQOvYkfy+PqSG0zlH/XvuH1xYa6rgqBFhngugxa2g8YoZ/FN0X1SERDU 9Z59bKPX9PiEmuMmakszHIcJzSW9Xx9dsSrqJBJ+JbVQDqL9HSIMkNIiovlQzZUBjqle ifNLJ+lo/lVs0WnE5A474Yfw5JZbO8T557D/vS+fC9RwSq8qbRJ+gf/vMhwPV0Pd1mUN X2JUfO5Mu51pzEOTPm7QtFQvbNMdpATZh6DJQDjnLNHckOo4kzxBdnnoxq9MXbbD+o24 GqRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731436823; x=1732041623; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VrmzWQrcfubT1wVvphopmQXKMuGUBxYX3etJgjkUDYw=; b=RGBAph9U5UmP+ASjvjhNyLS1ydCYBa9wzYtanGfQnRyeTOSZqJZjHs7ZXhAI7eMban ZxYXOMhd6Yj/MDhihTqCi5LTReq2YDR761yF+UkXRw6h+CVffoArgtFoenL5Rxc3xpc5 1tyxuGB9EAc6d16UhAW31goMW8wHhLwZlRB8Lh6n55BLIZEjLY+vCF4bRVCF+HNvKens BoTqE7dP584c1XY7VkquKdovrEnnQ+6sNuES7022aqP3Yg+KPlw+SRu1Z8ryYYNAzlDV qK2zZYOtUFd1WgwN1DXjqm5uEP2krfYAyMkBx8iPcwBTyPdeHjn3eBbTXSLoLasQiHf+ MG1A==
X-Forwarded-Encrypted: i=1; AJvYcCXX4JsrO/EBlw3+QHRba1vh+EM0LHsLD2mYKyqG7KJykmpID9eHyOQDbXOSXbd+cP5zKA/kiFhUUhHD5PM=@irtf.org
X-Gm-Message-State: AOJu0YyZWkeNSuyKBq6oADwmFBvtRsPvutY9YClaVA8Q2GzQfdpKaNWq QvJwpbXnUdZfhS99t/NQMsfPcodlRVkYxcW1gqs+0/6wBqICXZK7
X-Google-Smtp-Source: AGHT+IHZc+SCxDJxTtEpBxG63VG+O5dA7sYYyeY+mzzGXl5xACPMzCDduic76LhSyfEjxB3zQAtUpA==
X-Received: by 2002:a17:902:c403:b0:20c:5cdd:a91 with SMTP id d9443c01a7336-211ab9c4e94mr40340365ad.41.1731436823356; Tue, 12 Nov 2024 10:40:23 -0800 (PST)
Received: from smtpclient.apple (c-73-93-167-4.hsd1.ca.comcast.net. [73.93.167.4]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-21177ddd62csm96459005ad.59.2024.11.12.10.40.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2024 10:40:22 -0800 (PST)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <ZzOBaQSBNHxdugoV@faui48e.informatik.uni-erlangen.de>
Date: Tue, 12 Nov 2024 10:40:11 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2C1832C-26A8-4880-ADB7-85E685741C16@tony.li>
References: <CAFvDQ9ruuSkrxU4wQz21Ldfp4T4s2MnojJ3H9TFBHdBsQdZm5w@mail.gmail.com> <361466.1731421949@dyas> <ZzOBaQSBNHxdugoV@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: WBB3RPNAWITLJ2JMVIZ2MVIOPDMVUCHJ
X-Message-ID-Hash: WBB3RPNAWITLJ2JMVIZ2MVIOPDMVUCHJ
X-MailFrom: tony1athome@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: Michael Richardson <mcr+ietf@sandelman.ca>, E-Impact IETF <e-impact@ietf.org>, irtf-discuss@irtf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [irtf-discuss] Re: [Green] Re: [E-impact] 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/FyHcX4cQ-1F-QMD53aHXUSc6lAE>
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>

[-green, as this is inappropriate]


> On Nov 12, 2024, at 8:25 AM, Toerless Eckert - tte at cs.fau.de <mailforwards@cloudmails.net> wrote:
> 
> I was primarily thnking of provisioning powr for peak use. Or as necessary do
> peak shaving. For example, if there atually is a significant peak after e.g.
> a power failure, as there is in traditional servers with spinning disks, then
> this can typically be shaved through software/control mechanisms. I am not aware
> of anything like this for traditional network devices, but always good to
> know upfront that there is no such situation where power use is higher than
> power use during e.g.: 100% utilization, for which one does plan the power supply
> of the room/


Conventional high-end routing equipment already does a staged power-on sequence in order to reduce surge current at power-on. This is isolated to the system itself and does not span across systems. At cold boot, fans are necessarily spun up to full power to avoid worst-case situations. Once the ambient temperature can be ascertained and enough software is running to ensure that the system is not in thermal distress, fan power is reduced to maintenance levels.

Data sheet power usage for networking gear is typically peak, worst-case power utilization, as this is necessary for provisioning purposes.

T