Data, Technology & Verification Systems
Carbon-aware computing
Scheduling or relocating computing workloads to times and places where grid electricity is cleanest — cutting the carbon footprint of digital services without new hardware.
Expert review openNo editor-accepted expert review yetDefinition
The practice of adjusting when and where computation runs in response to the carbon intensity of electricity supply. Flexible workloads (batch processing, AI training, media encoding) are shifted toward hours or data-centre locations with lower grid carbon intensity, using carbon-intensity forecasts, while preserving service-level commitments.
References
System design; day-ahead carbon-intensity forecasts; virtual capacity curves; measured 1–2% power drops at peak-carbon hours.
Operational deployment; temporal and spatial workload shifting; 24/7 CFE linkage.
Overview
What it means
Pioneered at hyperscale by Google's Carbon-Intelligent Computing System (deployed from 2020; published 2021), carbon-aware computing exploits a fact of decarbonising grids: emissions per kWh vary hour to hour and region to region.
Google's fleet-wide implementation demonstrated measurable reductions in power draw at peak-carbon hours, and the approach pairs with the 24/7 carbon-free-energy goal of matching demand to clean supply every hour.
The concept has diffused into open-source practice via the Green Software Foundation's Carbon Aware SDK and into cloud carbon tooling, though measured effects remain modest where flexible load is a small share.
How it is used
Cloud providers and enterprises deploy carbon-aware schedulers; software engineers use carbon-intensity APIs (Electricity Maps, WattTime) to delay or relocate jobs; digital-sustainability reporting credits carbon-aware design as an operational mitigation measure.
Why it matters
As AI-driven compute demand surges, carbon-aware computing is one of the few levers that reduces digital emissions immediately, using the clean electricity already on the grid — a bridge to fully carbon-free operations.
Review
Public comments appear only after editor acceptance. Draft comments stay in the review queue.
Reviewers choose the definition or an overview paragraph, leave a comment or replacement, and attach evidence or a source link.
Editors compare reviewer cards side by side. AI may help find agreement, conflicts, unsupported claims and possible source issues.
Only an editor-accepted synthesis changes the public page. Reviewer identities are shown only with consent and verification.
Submitted reviews stay private until accepted.
Loading verified endorsements… Endorsements are not votes and never determine publication.
Endorse this definition
Endorse the exact version shown here. This is not a vote, and publication remains an editorial decision.
Review board
Comment on a specific line. Each reviewer stays separate until an editor accepts a merged draft.
Each person comments on the definition or overview in their own draft card, with role, evidence and suggested wording kept together.
AI can compare comments against the current text, flag conflicting claims, surface missing evidence and identify where reviewers agree.
An editor merges compatible suggestions into a draft change, checks sources, records disagreements and decides what can be published.