[E-impact] CASPER: Carbon-Aware Scheduling and Provisioning for Distributed Web Services

Hesham ElBakoury <helbakoury@gmail.com> Wed, 27 March 2024 01:21 UTC

Return-Path: <helbakoury@gmail.com>
X-Original-To: e-impact@ietfa.amsl.com
Delivered-To: e-impact@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32ABDC151091 for <e-impact@ietfa.amsl.com>; Tue, 26 Mar 2024 18:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 t3G7VVw84wlw for <e-impact@ietfa.amsl.com>; Tue, 26 Mar 2024 18:21:13 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66648C14F6B6 for <e-impact@ietf.org>; Tue, 26 Mar 2024 18:21:13 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id d9443c01a7336-1dee27acf7aso43783575ad.2 for <e-impact@ietf.org>; Tue, 26 Mar 2024 18:21:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711502471; x=1712107271; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=9HrG6XqP6G3jtE1RTkFfYpYZWzzHGz5v7s954ckyOpA=; b=P6DpAMd10oOCW12TRFCl9AI+G9q/UvLD9f4C8orRrI/ontROzamJLhlV8kSVFC6Azb BtZ3SCuxFPEbjXCAbr4BXaAhyZGZp4m59xINRTv3cQk3s5ahzRFXRCES7mb6o+YyagFF m4DERIPOclN48Vz624hWCEpriF03asZ9JEymU6Xm7uT4IBgFqeRvivu2P4QmhKeHEocb GvM5n7BFcrfwtU1mYlCEH+k9A/hlVPYJkf8FoV/YFXDKHK929BxLwunbInuQYpAPVwP7 OtDd7AWaNzWWd0VnwLGgGNbJ3uXn5wKiL4hXVe7M7WVeEjVu6H/zasszvRo7C5bMDPlT eObg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711502471; x=1712107271; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=9HrG6XqP6G3jtE1RTkFfYpYZWzzHGz5v7s954ckyOpA=; b=U4lZZIeJb7jQXUUJifjKjjjn7GNWPGCFWB/IfA2hsYg7/OE0TbuogD/b8RNckMJoI1 NpI2yTemQ1oVwps7b8c/TqOw7fedzpHz5GJezK3jGchvmQA8ZI8tV4yCcUp4qUVsMQil piuGSIMDEDaukczbRxF+IjXYPkoUuJ4TMcuZNBm388+HT0lAl120YNrq9DNtHF0VyVX9 VmMdym5TNZZRzmWDUrA3SyboNxm7r/S8evDfaMWqifOccHExZk+JbyKrcR3VTcxh0nOO hHYPhifDhRqwTCCi8XKYbPhwTlwMtDCzhJT7cz8qKrx0LpFCGcCuJWQYErxDWunFm3xo HxgQ==
X-Gm-Message-State: AOJu0Yx4jd/2060zAovYShaHvK3VejGWUpCoZlXeXQqe/DihWAfaTx2q 8EKYEqenYlahcdfOssTMSxF+hzBHxSb4kBSpxZ4mb0XdArBnCaRpvMKcOhD2+dOZLnVbfmC/B/B WEPLOd/OJKaxjqBIrKo+xRCN5dtA1x2Yp
X-Google-Smtp-Source: AGHT+IE0736KI/BStmppijtrSuZMmoyzw/2hHeHMYd/OpOY8PewbLJgjQbv050JYiqQpMQCRP3XMDty+4+9s5OUm1rE=
X-Received: by 2002:a17:902:e807:b0:1dd:8c28:8a97 with SMTP id u7-20020a170902e80700b001dd8c288a97mr1608519plg.6.1711502471145; Tue, 26 Mar 2024 18:21:11 -0700 (PDT)
MIME-Version: 1.0
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Tue, 26 Mar 2024 18:20:58 -0700
Message-ID: <CAFvDQ9rPEiLO-EByMVwgJ5XB=T4A88biB2U9NzK=1KgA-or-kw@mail.gmail.com>
To: E-Impact IETF <e-impact@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d330a906149a3834"
Archived-At: <https://mailarchive.ietf.org/arch/msg/e-impact/CLbXIJWh5KTETdci4mHgNByG3TQ>
Subject: [E-impact] CASPER: Carbon-Aware Scheduling and Provisioning for Distributed Web Services
X-BeenThere: e-impact@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Environmental impacts of the Internet <e-impact.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/e-impact>, <mailto:e-impact-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/e-impact/>
List-Post: <mailto:e-impact@ietf.org>
List-Help: <mailto:e-impact-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e-impact>, <mailto:e-impact-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2024 01:21:17 -0000

This new paper "*CASPER: Carbon-Aware Scheduling and Provisioning for
Distributed Web Services"* [1]. "CASPER is the first framework that
seamlessly integrates server provisioning and request scheduling for a
geo-distributed web application, with a particular focus on interactive web
requests."

*Abstract*
"There has been a significant societal push towards sustainable practices,
including in computing. Modern interactive workloads such as
geo-distributed web-services exhibit various spatiotemporal and performance
flexibility, enabling
the possibility to adapt the location, time, and intensity of processing to
align with the availability of renewable and low carbon energy. An example
is a web application hosted across multiple cloud regions, each with
varying carbon intensity based on their local electricity mix. Distributed
load-balancing enables the exploitation of low-carbon energy through load
migration across regions, reducing web applications carbon footprint. In
this paper, we present CASPER, a carbon-aware scheduling and provisioning
system that primarily minimizes the carbon footprint of distributed web
services while also respecting their Service Level Objectives (SLO). We
formulate CASPER as an multi-objective optimization problem that considers
both the variable carbon intensity and latency constraints of the network.
Our evaluation reveals the significant potential of CASPER in achieving
substantial reductions in carbon emissions. Compared to baseline methods,
CASPER demonstrates improvements of up to 70% with no latency performance
degradation."

What part of CASPER can be standardized by IETF?

Hesham
[1]
https://www.semanticscholar.org/paper/CASPER%3A-Carbon-Aware-Scheduling-and-Provisioning-Souza-Jasoria/85121825b5ecec7d234da96bf964b3926596e6d3?utm_source=alert_email&utm_content=AuthorCitation&utm_campaign=AlertEmails_DAILY&utm_term=AuthorCitation+LibraryFolder&email_index=34-0-58&utm_medium=31208820