How Is Cooling Designed for High-Density Data Centers?

Conventional air cooling — computer room air handlers (CRAH) on chilled water, or computer room air conditioners (CRAC) on direct expansion, delivering cold air through a contained hot-aisle/cold-aisle layout — comfortably handles traditional rack densities. The practical limit is airflow: pushing enough cold air through a rack, and getting the hot air back, gets exponentially harder as heat density climbs. Past roughly 30 to 50 kW per rack, air becomes impractical — fan energy soars, floor space for air handlers balloons, and hot spots appear no matter how good the containment is. The switch point is always a design calculation for the specific project, not a rule of thumb — but any rack layout pushing past 30 kW should trigger the liquid-cooling conversation on day one, because the architecture decision shapes the building: floor loading, water distribution, and heat rejection all change.

Liquid cooling removes heat at or near the source instead of asking air to carry it across the room. Three approaches dominate current design, and hybrid combinations of them with conventional air are the most common answer I see for mixed AI and general-compute halls. Every liquid design carries the same engineering obligations: water quality and treatment, leak detection and isolation, valving that lets a rack be serviced without draining the loop, and controls that coordinate the liquid and air sides as one system.

• Direct-to-chip: cold plates mount on processors and high-heat components, with a warm-water loop carrying heat to the rejection plant. Highest efficiency for AI racks; needs rack-level plumbing and leak detection.
• Rear-door heat exchangers: the rack's rear door becomes a water-cooled coil that captures exhaust heat at the source. Works with existing air systems — the leading retrofit path.
• Immersion: servers are submerged in dielectric fluid, single-phase or two-phase. Maximum density per square foot; demands structural review for fluid weight and rethought service procedures.
• Hybrid: air handling for general racks plus liquid for AI zones — the pragmatic answer for facilities mixing old and new IT.

PUE — power usage effectiveness — is the industry's efficiency scoreboard: total facility energy divided by IT equipment energy. A PUE of 1.0 would mean every watt goes to computing; everything above 1.0 is the overhead of cooling, power conversion, and lighting. Legacy facilities often ran 1.8 to 2.0. A well-designed modern facility lands around 1.3 to 1.5, and state-of-the-art designs approach 1.1 to 1.2. I treat PUE as a design target and a commissioning verification item: the engineering should state the design PUE basis, and the monitoring system should prove it in operation. An owner who never sees the number can't manage it.

• Containment — keeping hot and cold air separated is the cheapest PUE improvement available
• Economizers and free cooling — using outside air or water when conditions allow
• Variable-speed everything — fans, pumps, and compressors that track the actual load
• Matching the cooling architecture to the load — the right system at the right density
• Operations discipline — PUE is measured, not just designed; setpoints and sequences drift without attention

Heat has to go somewhere, and the rejection plant is designed around the local climate and water reality. Cooling towers reject heat evaporatively — efficient but thirsty. Dry coolers use no water but need more fan energy and larger footprints, and they lose capacity on the hottest days. Adiabatic and hybrid designs split the difference. In hot, arid climates, water availability and cost can decide the architecture outright, and WUE — water usage effectiveness — joins PUE on the owner's scoreboard. In California, the building systems around the IT load still answer to the 2025 California Energy Code / 2025 Standards, effective January 1, 2026 — efficiency requirements for the HVAC, lighting, and envelope don't disappear because the building houses servers. The energy model and the cooling architecture get developed together so compliance and performance describe the same facility.

• Cooling towers: lowest energy, highest water use — verify supply and cost first
• Dry coolers: zero water, larger footprint, derate in extreme heat
• Adiabatic/hybrid: water used only on peak days — the common arid-climate compromise
• The cooling plant is a major electrical load — mechanical and electrical designs must be sized together