AI, Energy, and the Geometry of Constraint
Why Power and Water Are Symptoms, Not the Root Problem
Abstract
Rapid growth in AI workloads has intensified scrutiny of data-center energy and water consumption. Much of the public discourse frames this challenge as a problem of efficiency.
This paper argues the opposite: energy and water consumption are emergent properties of compute geometry, not independent variables.
Claims of large, order-of-magnitude reductions in power or water usage are only meaningful when accompanied by explicit changes in where, when, and how heat is generated and dissipated across the system. Absent such structural reallocation, efficiency gains tend to relocate losses rather than eliminate them.
1. The Constraint Landscape
Modern AI systems operate under non-negotiable physical constraints:
Water usage in data centers is best understood within this context. It is not a primary driver of system behavior, but a secondary response to thermal density.
2. Why "Efficiency" Is an Incomplete Framing
Efficiency improvements are real and valuable. Techniques such as reduced numerical precision, sparsity and pruning, workload batching, and specialized accelerators can meaningfully reduce energy per operation within specific regimes.
However, these improvements share a common limitation: they operate within an existing geometry.
When overall demand grows faster than per-operation efficiency improves—as has been the case for AI workloads—total energy consumption continues to rise.
3. The Geometry Problem
At scale, AI infrastructure is governed less by individual components than by how those components are arranged.
Three geometric properties dominate outcomes:
1. Spatial concentration: High compute density produces high thermal density. Cooling demand scales non-linearly with concentration.
2. Temporal synchronization: Synchronous peak demand drives over-provisioning of both power and cooling capacity.
3. Centralized topology: Central aggregation of compute forces centralized heat rejection.
As long as these properties remain unchanged, reductions in power or water usage will be incremental, not transformational.
4. Water as a Symptom
Water consumption tracks thermal intensity, not intelligence.
Cooling systems use water because it is an effective medium for moving heat away from dense sources. When thermal density rises, water usage rises. When thermal density falls—through spatial distribution, temporal smoothing, or alternative dissipation paths—water usage declines naturally.
Attempts to "solve" water usage directly, without altering compute geometry, treat the symptom rather than the cause.
5. Structural Reallocation as the Primary Lever
Meaningful system-level reductions require structural reallocation:
Conclusion
AI infrastructure does not face a standalone water problem, nor a purely efficiency problem. It faces a geometry problem—one rooted in how energy, heat, and computation are arranged under immutable physical constraints.
Efficiency matters. Cooling matters. But structure decides.