Introduction
AI training runs can consume substantial electricity, and that electricity often has a water footprint. Water may be used directly at the data center (for example, evaporative cooling or cooling towers) and/or indirectly upstream (for example, water used in electricity generation, fuel extraction, or thermal power plant cooling). This calculator provides a clear, browser-based estimate of total energy and associated water use for a single training job using four inputs you can usually obtain from monitoring, vendor specs, or facility reporting.
The result is best treated as an order-of-magnitude estimate for planning, comparisons, and communication. If you have facility metering or audited sustainability data, use those values for the most accurate output. If you are comparing two options, the calculator is most useful when you keep the same boundary and methodology for both scenarios.
How to use
- Enter average training power draw (kW): use the average power over the run (not peak). If you only have energy logs, you can compute average kW as total kWh divided by hours.
- Enter training duration (hours): the total active runtime at roughly the stated average power. If training pauses or scales up/down, use the best average across the full window.
- Enter data center PUE: this scales IT energy to total facility energy (cooling, power conversion, lighting, and other overhead). A lower PUE generally means less overhead energy for the same IT work.
- Enter water use per kWh (litres): choose a factor that matches your scope (on-site only, or on-site + upstream). If you are unsure, start with a mid-range value and refine later using provider disclosures or regional grid data.
- Select Calculate water use to see total energy (kWh), estimated water use (L), and an equivalent number of 500 mL bottles.
Formula
This calculator uses a simple linear model:
Total facility energy (kWh) = Power (kW) × Time (hours) × PUE
Total water use (L) = Total facility energy (kWh) × Water per kWh (L/kWh)
In compact form:
- P = training power draw (kW)
- T = training duration (hours)
- PUE = power usage effectiveness (dimensionless)
- WPK = water use per kWh (L/kWh)
- W = total water use (L)
Worked example
Assume a training run with:
- Power draw: 30 kW
- Duration: 48 hours
- PUE: 1.3
- Water per kWh: 1.8 L/kWh
- Facility energy = 30 × 48 × 1.3 = 1,872 kWh
- Water use = 1,872 × 1.8 = 3,369.6 L (about 3,370 L)
- Equivalent 500 mL bottles = 3,369.6 ÷ 0.5 = 6,739 bottles (rounded)
If you rerun the same job in a facility with the same PUE but a lower water intensity (for example, 0.8 L/kWh), the estimated water use becomes 1,872 × 0.8 = 1,497.6 L. That illustrates why the litres-per-kWh assumption is as important as the energy estimate when you are comparing locations.
Assumptions and limitations
- Average values: power draw and PUE are treated as constant averages; real runs vary over time and may include idle periods, checkpointing, or data pipeline bottlenecks.
- Your water factor defines the scope: the litres-per-kWh input may represent on-site cooling water, upstream electricity water, or both. Document your choice when sharing results so others can interpret it correctly.
- Local context matters: the same litres can have different impact depending on water scarcity, seasonality, and source. This tool estimates volume only; it does not model scarcity-weighted impacts.
- Not a compliance tool: use audited metering and applicable standards for formal reporting. This page is intended for internal planning, education, and quick comparisons.
Definitions (plain language)
Because sustainability terms are often used inconsistently, here are the definitions assumed by this calculator. These are not the only valid definitions, but they are common and practical for scenario modeling.
- Training power draw (kW): the average electrical power used by the training workload’s IT equipment. Depending on your boundary, this may include GPUs/TPUs, CPUs, memory, storage, and networking that are dedicated to the job.
- Training duration (hours): the time window during which the job is consuming the stated average power. If you have a job scheduler, this may be the wall-clock runtime; if you have energy logs, it may be the interval over which energy was measured.
- PUE: a ratio of total facility energy to IT energy. A PUE of 1.3 means that for every 1.0 kWh used by IT, the facility uses 0.3 kWh extra for overhead such as cooling and power conversion.
- Water use per kWh (L/kWh): a user-supplied factor that converts energy into water volume. It can represent on-site cooling water, upstream electricity water, or a combined estimate. The calculator does not enforce a specific scope; you choose the factor that matches your reporting needs.
What the result means (and how to compare scenarios)
The output combines your IT workload (power × time) with facility overhead (PUE) and a water-intensity factor (L/kWh). Because the model is linear, doubling any one input doubles the estimated water use. That makes the calculator useful for quick comparisons such as:
- Facility comparison: keep power and duration constant, then vary PUE and litres-per-kWh to compare regions or providers.
- Workload planning: adjust power and duration to represent different model sizes, hardware generations, or training schedules.
- Efficiency improvements: estimate the impact of lowering PUE or switching to a lower-water cooling approach (reflected in a lower L/kWh factor).
When comparing scenarios, the most common mistake is mixing scopes. For example, one source might report on-site cooling water only, while another includes upstream electricity water. The calculator will still compute a number, but the comparison may be misleading unless you align the definition of “water per kWh.”
Typical input ranges (starting points)
If you do not have measured values yet, these ranges can help you choose reasonable initial inputs. Replace them with facility-specific data whenever possible.
- Power draw (kW): a single server is often ~1–3 kW; a multi-accelerator node may be ~5–10 kW; rack-scale training can be 20–50+ kW; multi-rack clusters can be hundreds of kW or more.
- Duration (hours): experiments may run for minutes to hours; full training runs can run for days or weeks. If you are estimating a multi-phase run (pretraining + fine-tuning), you can compute each phase separately and add the results.
- PUE: highly optimized facilities may be ~1.1–1.3; many modern sites are ~1.3–1.6; older sites can be 1.6+ depending on climate and design.
- Water per kWh (L/kWh): varies widely by cooling approach and electricity mix. Values around 0.5–4 are commonly used for rough scenario modeling, but local values can be outside that range.
Illustrative comparison table
The table below shows how PUE and water intensity change the result for the same training power and duration. Values are illustrative only.
| Scenario | PUE | Water use per kWh (L/kWh) | Relative water use (same power & time) |
|---|---|---|---|
| Efficient, low-water facility | 1.2 | 0.5 | Low |
| Efficient, moderate-water facility | 1.2 | 1.8 | Moderate |
| Average facility | 1.4 | 1.8 | Higher |
| Less efficient, high-water facility | 1.7 | 3.0 | Significantly higher |
Practical tips for better estimates
- Use averages: if power varies, use an average over the run (or compute energy from logs and back-calculate an average kW).
- Be explicit about scope: decide whether your L/kWh includes only on-site cooling water or also upstream electricity water.
- Record assumptions: when sharing results, note the PUE source and the water-intensity source (provider report, utility data, internal estimate).
- Compare like-for-like: keep the same scope and methodology when comparing regions or providers.
- Consider seasonality: some facilities use more water in hotter months; if you are planning a long run, consider whether your factor should reflect a seasonal average.
- Separate phases: if your run includes pretraining, fine-tuning, and evaluation with different power profiles, calculate each phase separately and sum the litres.
Interpreting “water use” responsibly
Water accounting can be confusing because “use,” “withdrawal,” and “consumption” are not always the same. Many sustainability reports distinguish between water withdrawn (taken from a source) and water consumed (not returned to the same watershed in the same quality/quantity). Evaporative cooling tends to increase consumption because water leaves the system as vapor. Other cooling approaches may withdraw water but return most of it. This calculator does not attempt to resolve those definitions; it simply multiplies energy by a litres-per-kWh factor that you provide.
For that reason, the most important step is to label your factor. If your factor represents on-site cooling water consumption, say so. If it represents upstream electricity water consumption, say so. If it is a combined estimate, note what is included. Clear labeling makes the output useful even when the number is uncertain.
Frequently asked questions (practical)
Should I include only GPU power, or the whole cluster?
Use the boundary that matches your goal. For internal engineering comparisons, you might use the training cluster’s measured power (GPUs plus supporting servers and networking). For facility planning, you may want the full IT load attributable to the job. The calculator then uses PUE to estimate facility energy from that IT energy.
What if I already know total energy in kWh?
If you already have total IT energy, you can convert it to an average power by dividing by hours, then enter that average kW and the same hours. Alternatively, you can set PUE to 1.0 if your kWh already represents total facility energy rather than IT energy. The key is to avoid double-counting overhead.
Does a lower PUE always mean lower water use?
Not necessarily. PUE measures energy overhead, not water intensity. A facility can have a low PUE but still use a lot of water if it relies heavily on evaporative cooling, or if the electricity supply has a high upstream water footprint. That is why this calculator keeps PUE and litres-per-kWh as separate inputs.
How can I reduce the estimated water footprint?
In this model, you can reduce water by reducing any of the four multipliers: lower average power (more efficient hardware or better utilization), shorter duration (fewer training steps or faster convergence), lower PUE (more efficient facility), or lower water intensity (cooling approach and electricity mix). In practice, the most effective lever depends on your constraints and where you can make changes.
Summary
This calculator is intentionally simple: it turns a training run’s average power and duration into energy, scales by PUE to approximate facility energy, and converts energy to water using a litres-per-kWh factor that you control. Use it to explore “what if” scenarios, to communicate assumptions clearly, and to identify which variable matters most for your situation.