Showing posts with label Sustainability. Show all posts
Showing posts with label Sustainability. Show all posts

Sunday, October 4, 2026

The Trout Stream Under the Turnpike, and the Data Center Over the Barnes Aquifer

Image source https://tinyurl.com/2t3kumjt
When my Dad drove me, he let me out at East Mountain Golf Course. He said to be home for supper. I said I would. He drove off and I went down to the water.

I was ten when I first fished it. The stream came out of the woods below the golf course. It was small and cold and clear. You could step across it in three places. I fished it downstream, one pool at a time, and I kept low and quiet. The brook trout were native and they had been there longer than the golf course, the turnpike and the town. They were dark on the back and orange on the belly, with white edges on the fins. I kept a few. I put the rest back.

I never saw another person on it. There were no boot prints in the mud and no line in the branches. No beer cans, no bait tins. The golfers stayed on the fairways and the people in the cars on the turnpike never looked down. I think I was the only one who ever fished that section. I told no one. My friends did not know. I kept it to myself and the trout stayed where they were.

There was a pool in the woods where the stream bent against a root bank. It was deep on the outside of the bend and slow. A big brook trout lived there. I saw the fish the first time as a shadow that moved when I moved. I put a worm over the edge of the current and let it drift under the roots. The trout took it hard.

It was the biggest brook trout I had ever seen. Its belly was deep orange. Its back was dark green with pale spots, and the red spots had blue rings around them. I held the trout in the water and it stayed there a moment, then it went. I let it go. I could have kept it. I let it go anyway.

I caught the trout several times that way. I knew it by the size and by the pool. Each time I let it go. Nobody else knew it was there, so nobody else would have let it go.

The woods got thick below the pool and I followed the stream through them. Then the Massachusetts Turnpike came over the top and the stream went into a tunnel. Trucks ran overhead and the concrete shook a little. Inside it was dark and loud and the water was colder than outside. I waded in with the rod held low. The big brown trout lived under there. They held in the current, facing upstream, and waited for the water to bring them something to eat. Sometimes I could see them. They were always hard to catch. I caught a few over the years and let every one go. The one I remember best, I lost. I had hooked a big brown and I had no net. I never carried a net because it tangled in the brush. I had the trout in my hand. It flipped its tail and spat the hook. I was going to let it go anyway. Still. I stood in the dark a while after that.

On the other side the stream came out into the light and ran on to the railroad tracks. There I left it. I climbed the cinders and walked the rails home to 342 Holyoke Road. The ties were spaced wrong for my legs. I walked them anyway.

When my Dad did not drive me, I went the other way. I left the house in the morning and cut through the woods to the tracks. I followed the rails until the stream passed under them. I started there and fished upstream toward the tunnel, and then on to the pool. My Mom knew the time to expect me and that was enough.

The water was cold in July. It came out of the ground that cold and stayed that cold all summer. I never wondered why. A boy does not wonder about water that works. I know now where it comes from. It comes from the Barnes Aquifer, and I fished it for years without knowing its name.

The last time I fished the stream was (I think) the summer between my sophomore and junior years of college. That was about fifty years ago. By then I had switched to a 1 weight 7 foot 6 inch fly rod. The trout in that stream always ate up hellgrammite pattern flies. My parents' house sold last month, and I doubt I will fish it again. I wrote about the sale and the empty rooms.

Thousands of cars cross the stream every day on the turnpike. I doubt anyone knows it is there. I always look. I can see a small section of it. It looks like beavers have dammed part of it. They found the stream too.

I do not know if the brook trout are still there. The big one is gone. Brook trout seldom live past five years. I do not know if the water is still cold in July.

A data center campus is now proposed over the aquifer. In 2021, the Westfield City Council approved a $4 billion campus at 199 Servistar Industrial Way, 1.8 miles from my childhood house. The vote passed 9 to 3. The site sits partly on wetlands and directly over the Barnes Aquifer, the region's municipal drinking water source. In July 2026, the council voted unanimously for a one year moratorium on new data centers. The campus would draw 274 megawatts.

Servistar says it plans a closed-loop cooling system. The reporting I reviewed does not name the cooling vendor or design. NVIDIA's current liquid cooling design uses dry coolers and claims zero water consumption on site. Dry coolers can demand 10 to 35 percent more electricity than evaporative towers. Lawrence Berkeley National Laboratory found that 92.5 percent of a data center's water footprint comes from generating its electricity. Servistar's plans include natural gas generators. I covered the engineering in more detail in my post on NVIDIA's cooling design.

State certification standards will require the developer to disclose cooling method, power source, and noise mitigation before construction proceeds.

I do not know what the campus will do to the stream. Brook trout need cold water, and that stream ran cold because of the aquifer. I never told anyone about it. I am telling you now, so that when the disclosures come out, you know a stream runs under the turnpike on that water.

Friday, October 2, 2026

Inside NVIDIA's 113-Degree Cooling Design, and Westfield's Data Center Question

Given the strong debate and varied perspectives surrounding the proposed Westfield (my hometown) data center campus, this post focuses strictly on verifiable technical specifications and empirical data as I understand it. The goal is to provide an objective, fact-based overview of the project's engineering parameters, NVIDIA's recent high-temperature liquid cooling design, local climate limits, and broader infrastructure trade-offs. Read my earlier post on the topic here.

I grew up at 342 Holyoke Road in Westfield, Massachusetts. In 2021, the City Council approved a $4 billion data center campus at 199 Servistar Industrial Way, 1.8 miles from that house. The vote passed 9 to 3. The site sits partly on wetlands and directly over the Barnes Aquifer, the region's municipal drinking water source. In July 2026, the council voted unanimously for a one year moratorium on new data centers, and the campus would draw 274 megawatts. Servistar says it plans a closed-loop cooling system. The reporting I reviewed does not name the cooling vendor or design.

In June 2026, NVIDIA published a cooling design that addresses the same question. It appears in the DSX reference design, a guide for building the full AI factory infrastructure stack. NVIDIA's Ali Heydari says the design has zero water consumption and has eliminated most power use for cooling. NVIDIA's own description of the Vera Rubin NVL72 system calls it single-phase direct liquid cooling with a 113°F supply temperature.

Earlier liquid-cooled deployments supplied water in the 80°F to 90°F range. Those systems cooled the CPUs and GPUs with cold plates and left other components to air. Rubin cools every chip and networking component by liquid, eliminating fans inside the server chassis and compute racks. The coolant is a 75 percent water and 25 percent propylene glycol mix that enters the chip at 113°F and leaves near 131°F. Operators have traditionally recommended an ambient temperature of 64°F to 81°F. NVIDIA's summary also lists a 6U system now fitting in 2U and no hot or cold aisle management.

Inside the building, a Cooling Distribution Unit (CDU) uses a liquid-to-liquid heat exchanger to isolate the secondary coolant loop in the server racks from the primary facility loop. The primary loop then carries heat outside to dry coolers. NVIDIA says they reject heat efficiently for much of the year and that the loop avoids evaporative cooling 99 percent of the time. In favorable climates, NVIDIA says this cuts water use from roughly 2.6 million gallons per megawatt per year to near zero. Hotter climates such as Phoenix may still need chillers on peak summer days. The captured heat can also be reused to warm nearby buildings.

Heat path from chip to outdoor air. Coolant temperatures are NVIDIA figures.

Westfield's climate aligns with the thermal operating requirements for those dry coolers. The average July high is 83°F, and the average January high is 34°F. Barnes Municipal Airport recorded a high of 98.1°F in July 2026. Because fluid leaves the chips near 131°F and typical heat exchangers require a 5°F to 9°F approach margin, outdoor air only needs to remain below about 104°F to supply 113°F coolant back to the racks. As a result, dry coolers in Westfield can maintain a 113°F supply temperature year-round without requiring supplemental mechanical chillers. Nearby Springfield has gained 11 more above-average summer days since 1970, but local peaks remain within the system's thermal operating limit. A campus drawing 274 megawatts releases close to that much heat, and dry coolers send it to outdoor air.

Westfield outdoor temperatures compared with coolant temperatures. The 104°F limit is an estimate.

NVIDIA estimates that a 50MW facility saves over $4 million a year in cooling energy and water. Cooling has accounted for up to 40 percent of a data center's electricity. One reviewer notes the capital cost premium over air cooling remains unknown.

Environmental and energy analyses point out that on-site claims exclude water consumed by off-site power plants supplying the grid. Lawrence Berkeley National Laboratory found that 92.5 percent of a data center's water footprint comes from generating its electricity. Dry coolers can also demand 10 to 35 percent more electricity than evaporative towers. Servistar's plans include natural gas generators, and Westfield Gas & Electric estimates a gas pipeline at about $20 million.

State certification standards will require the developer to disclose cooling method, power source, and noise mitigation before construction proceeds. 

Every source is linked above for you to read and weigh.

Wednesday, August 19, 2026

What Nobody Tells You About AI and Your Water Supply

Last week during a workshop on AI tools in the classroom at Pace University, a faculty member asked about AI and water use. I expected the question. The workshop was about classroom applications, not infrastructure, so I kept the answer short and moved on. Here’s a longer answer.

Data centers consume water directly, through cooling towers that evaporate it to remove heat. US data centers directly consume an estimated 17 to 19 billion gallons a year, a figure projected to climb toward 60 to 110 billion gallons by 2030. The bigger draw is indirect. Generating the electricity these facilities use consumed roughly 211 billion gallons of water in 2023, mostly through cooling at power plants. A data center's water footprint depends as much on how its power is generated as on how its servers are cooled.

Location compounds the problem. Two thirds of new data center construction since 2022 has landed in areas already under water stress. Municipal systems supply nearly all of that water, and the infrastructure upgrades to meet rising demand often fall on residential ratepayers rather than the companies building the facilities. Transparency has not kept pace either. Most operators disclose only partial or aggregate figures, so the public rarely sees facility level numbers.

The fixes already exist - sort of. Closed loop and liquid cooling systems cut water draw at the facility to near zero. Siting near hydro, nuclear, or wind power removes most of the indirect draw tied to electricity generation. The Massachusetts Green High Performance Computing Center in Holyoke, built in 2012 on hydro power from the Connecticut River, has been proving this model for over a decade. But.... scale matters here. MGHPCC runs on a 15 to 19 megawatt connection with about 10 megawatts dedicated to computing. A single hyperscale AI campus now under construction can draw a gigawatt or more, one hundred times that load. Holyoke proves the cooling and power sourcing approach works. It does not prove that approach scales directly to a facility built for AI though.

Regulation is starting to catch up. State legislatures introduced more than 200 data center bills in 2025 and enacted over 40 of them across 21 states. Most of what passed addressed ratepayer protection and siting incentives rather than water directly. Roughly 30 of the proposed bills targeted water consumption specifically, and only a handful of those were enacted. South Carolina and Kansas are considering mandates requiring closed loop cooling. California, Iowa, and Michigan are pushing water use disclosure requirements. Virginia is taking a different route, tying grant funding to the use of reclaimed wastewater instead of potable water in cooling systems. None of this is settled yet. Water legislation is still catching up to where energy legislation was two years ago, and disclosure requirements are starting to follow the path carbon reporting took a decade earlier.

I told that faculty member the honest version this week: the technology to fix this exists, and it works today in Holyoke. Scaling it up is an engineering problem, and engineers solve those. What is missing is the will to require it before the next facility breaks ground.