G-P10 · TOPIC · compute-energy-waterGCRI dossier · service level R0
GCRIData and ComputeIn development
Topic dossier · Data and Compute

Compute energy water

Data centres and supercomputers consume electricity for computing and cooling, and many use water for cooling directly or through power generation. As demand grows, they affect grids, water resources and emissions in the places they are built. This page sets out how computing uses energy and water, how efficiency is measured with standard metrics, and what evidence serves the operators, regulators and planners concerned.

01In brief

The short answer.

Data centre energy and water use is the electricity and water consumed by computing facilities for processing and cooling. Cooling choices trade water against energy, clusters of facilities can strain local grids and water, and waste heat can be reused. Standard metrics such as PUE and WUE describe efficiency within stated boundaries.

02Geography

Water now in the contiguous United States.

For compute energy water, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with a past-year temperature and sunshine chart at the centre, framed on the contiguous United States; every other NASA layer, live feed and forecast waits in the layer list.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 3

Water now, for this page

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

For compute energy water, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with a past-year temperature and sunshine chart at the centre, framed on the contiguous United States; every other NASA layer, live feed and forecast waits in the layer list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONET · GDACS · Copernicus Sentinel-2 L2ASources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). CC BY 4.0
  • MODIS land products (vegetation indices, gross primary production, land cover), NASA LP DAAC and LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
  • Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
  • Live: NASA EONET Events are indicative, not official warnings.
  • Live: GDACS (EC JRC / UN OCHA) Events are indicative, not official warnings.
  • Observed (EO): Copernicus Sentinel-2 L2A (contains modified Copernicus Sentinel data 2026), Microsoft Planetary Computer
  • Optional layers (35 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026
  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • Land cover type (IGBP), yearly: MODIS Terra and Aqua land cover (MCD12Q1), NASA LP DAAC · 2024
  • Land surface temperature, day, 8-day composite: VIIRS NOAA-20 Level 3, 8-day, NASA LANCE · 14 Sep 2026
  • Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026

03Console

Compute facility console, in outline.

The working screen behind this subject: its structure, terms and states. Names are placeholders and values illustrative.

Compute facility console

Compute energy water · HPC facility · Month 12

  • Utilisation, % of nodes
    76Active
  • PUE
    1.24Normal
  • WUE
    0.3l/kWhWatch
  • Queue wait, p50
    3.9h
Cooling water near permitGCRI · Data and Compute

Energy by use

  • IT load
  • Cooling
  • Other

Allocations

Climate ensemble724985Near quota
Flood modelling437587Within
Genomics pipeline282224Near quota
Compute facility console: the screen's structure, terms and states for Compute energy water.Placeholder names and illustrative values; a design, not a record or a live system.
04The question

Compute energy water: how the risk develops.

Infrastructure impacts and sustainability. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.

Mechanism

Electricity is the main input

Servers, storage and networking draw power continuously, and cooling adds overhead. Total demand depends on workload growth and efficiency gains.

Mechanism

Cooling choices trade water for energy

Evaporative cooling uses less electricity but consumes water; air and closed-loop liquid cooling use less water but may use more energy.

Mechanism

Siting concentrates impact

Clusters of data centres in one region can strain local grids and water supplies even when national totals look modest.

Mechanism

Heat can be reused

Waste heat from computing can supply district heating where networks exist nearby, turning a loss into a resource.

05Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Water usage effectivenessSite water use divided by IT equipment energy, a standard data centre metric.
Evaporative coolingCooling by evaporating water, which saves energy but consumes water.
Waste heat reuseUsing heat from computing for other purposes, such as district heating.
06Indicators

What is measured, and how well.

Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.

IndicatorUnitCadenceSource typeLabel
Power usage effectivenessratio of total facility to IT energyannualOperator reporting under ISO/IEC 30134-2DECLARED
Water usage effectivenesslitres per kilowatt hour of IT energyannualOperator reportingDECLARED
Data centre electricity consumptionterawatt hoursannualEnergy agency estimatesESTIMATED
Renewable energy sharepercent of electricityannualOperator reportingDECLARED
Waste heat reusedmegawatt hoursannualOperator reportingDECLARED
Data centre share of regional electricity demandpercentannualGrid operator dataESTIMATED
07Canvas

From sources to decisions.

The topic as a computational graph: named sources feed the methods, an evidence review gates the outputs, and the decisions stay with the authorities that hold them.

Pipeline canvas · Compute energy water as a run graphDesign, not a record
Compute energy water: build, test and release in Nexus FoundryA request opens a workspace; data are ingested and validated; the model is built and tested on held-out data; an independent gate approves release with limits; the workspace is stood down and the record kept. Design of the process, not a record of a run.

Fig. 02Nodes carry their type, two metric rows and a state; connectors show what feeds what; dashed frames name the owners; the timeline is the cadence. Design of the pipeline, not a record of a run.

08Sources

Where the evidence comes from.

Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.

SourceWhat it givesLicence class
EU data centre reporting under the Energy Efficiency DirectiveEnergy, water and efficiency data from EU data centresPublic summaries, EU terms (to check)
IEA data centre electricity estimatesGlobal and regional demandLicence per product (to check)
Uptime Institute global data centre surveyIndustry practices and efficiency trendsPublic summaries, terms to check
Green500 listEnergy efficiency of supercomputersPublic, TOP500 terms
Grid operator load forecastsExpected data centre loadPublic records, terms per operator
09Decisions

Who decides, and what the evidence serves.

Data and Compute prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.

Who decidesThe questionEvidence this page serves
Energy regulators and grid operatorsHow to plan connections and supply for data centresRegional impact analyses
Water authoritiesWhether proposed cooling water use is sustainableWater footprint evidence
Operators and public computing centresWhich cooling and heat reuse options to adoptFootprint methods; heat reuse maps

Outputs this topic produces

  • Energy and water footprint methods for computing facilities
  • Regional grid and water impact analyses
  • Heat reuse opportunity maps
  • Evidence notes on efficiency reporting
10Core questions

What experts ask about compute footprints.

  • How much additional grid capacity will new data centres need, where and when?
  • How much water does cooling use, directly and through electricity generation, and in which catchments?
  • Can computing loads be shifted in time or place to match renewable output or avoid grid peaks?
  • Can waste heat be reused, for example in district heating?
11Mechanisms

How computing draws on energy and water.

Nearly all the electricity a computer uses becomes heat that must be removed. Cooling methods range from air cooling to liquid cooling and evaporative systems. Evaporative cooling uses water efficiently for energy but consumes water; dry cooling saves water but uses more electricity, especially in hot weather. The choice is a local trade-off between energy and water.

Large data centres are concentrated, steady loads that can require new transmission and generation. Their growth can compete with housing, industry and electrification for grid connections. Heatwaves stress both the grid and cooling systems at the same time, a common-cause risk for continuity. Some workloads, such as model training or batch analysis, can be scheduled flexibly; others, such as real-time services, cannot.

12Methods and limits

How footprints are measured and planned.

  1. 01

    Efficiency metrics

    Ratios of total facility energy to IT energy, and water use per unit of IT energy. Limits: they say nothing about whether the computing itself is efficient or useful.

  2. 02

    Load forecasting

    Projecting data centre demand for grid planning, with power systems engineering. Limits: announced projects often exceed what is built, making forecasts uncertain.

  3. 03

    Life cycle assessment

    Accounting for manufacturing, operation and disposal, drawing on energy technology. Limits: data on hardware manufacturing is limited.

  4. 04

    Flexibility analysis

    Assessing how much load could shift. Limits: depends on workload types and contracts.

14Questions

Questions and answers.

What is PUE?
Power usage effectiveness: total facility energy divided by IT equipment energy, defined in ISO/IEC 30134-2. A value of one would mean no overhead.
Do data centres use a lot of water?
Some do, especially with evaporative cooling in hot climates. Water use depends on cooling technology, climate and the electricity supply.
Can data centre heat be reused?
Yes, where district heating or other heat users are nearby, waste heat can be supplied to them, as some European facilities do.
Is water use always a problem for data centres?
It depends on the local water situation and the cooling design. In water-stressed areas, water use matters greatly; elsewhere, energy use may be the bigger concern.
Can data centres help the grid?
Potentially, through flexible scheduling of some workloads, backup power and waste heat reuse. The extent depends on design and agreements.
Does the platform publish facility-level data?
Only where operators have published it. It does not collect confidential facility data for publication.
Data and Compute

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.