- Meter power
- 100 MW
AssumedAssumed: Modeled campus size, set by the reader. Why
- American homes, same power
- ≈83,000
Calc.Calculated: Homes = meter kW ÷ 1.2 kW, a round figure for the average continuous electricity draw of an American home (1.2 kW × 8,760 hours ≈ 10,500 kWh a year), rounded to two figures. For scale only. Method
- US grid losses, 2018–2022
- ≈5% (EIA)
ReportedSources: U.S. Energy Information Administration FAQ answer: "annual electricity transmission and distribution (T&D) losses averaged about 5% of the electricity transmitted and distributed in the United States in 2018 through 2022"
- 1,000 km, propagation only
- ≈5 ms one way, ≈10 ms round trip
Calc.Calculated: One-way delay = 1,000 km × the fiber-speed figure above (≈4.9 µs/km) ≈ 5 ms; round trip doubles it to ≈10 ms. Switching, routing and queueing are not included. Method
- DeepMind Decoupled DiLoCo
- 4 US regions over 2–5 Gb/s
ReportedSources: Google DeepMind blog post: "We successfully trained a 12 billion parameter model across four separate U.S. regions using 2-5 Gbps of wide-area networking"
- Voltage
- 345 kV line-to-line
AssumedAssumed: Campus interconnection voltage, 345 kV. Why
- Current, 100 MW
- ≈90 A per phase, on each circuit
Calc.Calculated: Per-phase current on each of two equally loaded circuits = campus MW ÷ (2 × √3 × 345 kV × power factor). Method
- Same power at 415 V
- ≈146,000 A
Calc.Calculated: Current = meter W ÷ (√3 × 415 V × 0.95) for three-phase AC, at the same 0.95 power factor the voltage staircase uses, or meter W ÷ 800 V for DC, rounded to the nearest thousand amps. It shows why power travels at high voltage; no conductor carries a whole campus at rack voltage. Method
- Rating
- 3 × 75 MVA, N+1
Calc.Calculated: Count = ceil(campus MW ÷ (transformer unit MVA × assumed 0.95 power factor)) + 1 spare (N+1); the model buys 300 MVA units above 400 MW and 75 MVA units below. Method
- Efficiency, 345 kV class
- >99.6% at all loading levels
SpecSources: PA Transformer product page: "High efficiency: exceeding 99.6% at all loading levels"
- Loss at 100 MW
- ≈0.4 MW
Calc.Calculated: Loss = campus MW × (1 − main-transformer efficiency). Method
- Units here
- ≈40, N+20%
Calc.Calculated: Units = ceil(campus MW ÷ 3 MW × 1.2) for N+20% redundancy on 3 MW-class sets. Method
- Size here
- ≈20 MW / 40 MWh
Calc.Calculated: Power = 0.2 × campus MW; energy = 0.4 × campus MW (a 2-hour duration at that power) — a round sizing this model picks to show scale, not a vendor design. Method
- Cooling power
- 4.4 MW
Calc.Calculated: Cooling power = coolFrac × IT MW, where coolFrac is calibrated so each cooling design lands in its publicly reported PUE band once the power chain’s own losses are added. Method
- PUE, this design
- 1.14
Calc.Calculated: IT MW solves meter MW × upstream efficiency = IT MW ÷ IT-path efficiency + (cooling fraction + misc fraction) × IT MW ÷ side-path efficiency, chaining the model’s own conversion efficiencies; PUE = meter MW ÷ IT MW. Method
- Water on site, a day
- ≈336 m³
Calc.Calculated: Water = WUE (L/kWh IT) × IT MW × 24 h, converted to cubic meters. Method
Assumed: Water use by cooling design, air 1.0, liquid 0.5, warm water 0.16 L/kWh IT. Why
- Efficiency, Eaton 9395XR
- up to 97.5% online, 99% eco
ReportedSources: CEIE (distributor reprint of Eaton figures) "tested efficiency of Eaton 9395XR UPS dual conversion in online mode is as high as 97.5%"; eco/AC-direct mode "can be improved to 99%" (Eaton’s own product page could not be opened this pass -- see its unchecked note)
- Loss at 100 MW
- ≈3.2 MW
Calc.Calculated: Loss = the downstream load this stage feeds ÷ its assumed efficiency, minus that load itself. Method
Assumed: UPS double-conversion efficiency, 96.5%. Why
- IT load
- 88 MW
Calc.Calculated: IT MW solves meter MW × upstream efficiency = IT MW ÷ IT-path efficiency + (cooling fraction + misc fraction) × IT MW ÷ side-path efficiency, chaining the model’s own conversion efficiencies; PUE = meter MW ÷ IT MW. Method
- Compute racks, campus
- 629 × ≈131 kW = 83 MW
Calc.Calculated: Racks = floor(IT MW × 1000 ÷ (one rack’s kW + its GPUs’ share of the fabric’s kW)). Method
- Network, switches and optics
- 5.0 MW
Calc.Calculated: MW = a published or estimated per-unit power (per switch or per optical module) × how many units this campus’s fabric needs for its GPU count. Method
- GPUs
- 45,288
Calc.Calculated: GPUs = racks × GPUs per rack. Method
- Scale-out switches, 3 tiers
- 2.7 MW
Calc.Calculated: MW = a published or estimated per-unit power (per switch or per optical module) × how many units this campus’s fabric needs for its GPU count. Method
- Optical transceivers
- 2.3 MW
Calc.Inputs: NVIDIA section 4.2, Recommended Operating Conditions and Power Supply Requirements: Maximum Power Dissipation, Max 17 W (the 400G-class per-module figure the fabric model scales from)
Calculated: MW = a published or estimated per-unit power (per switch or per optical module) × how many units this campus’s fabric needs for its GPU count. Method
- Fabric strands, whole campus
- ≈1.1 million
Calc.Calculated: Physical endpoints = GPUs × scale-out NICs per GPU (two for Rubin, one for the other modeled generations). The selected fabric uses each physical port’s rate, not aggregate per-GPU bandwidth. Switch, module and fiber counts follow that endpoint inventory and the modeled tiers. Method
- Efficiency
- ≈97.5% peak
SpecSources: Flex product page: "High efficiency up to 97.5% (peak)"
- Busbar current
- ≈2,600 A
Calc.Calculated: Current = rack DC bus power ÷ busbar voltage. Method
- Per GPU
- NVLink 5, 1.8 TB/s
SpecSources: NVIDIA "The revolutionary 1.8 TB/s of bidirectional throughput per GPU"
- Trays
- 9, 2 switch chips each (18)
SpecSources: NVIDIA Hardware: "18x 1RU compute trays, each with 2 Grace CPUs and 4 Blackwell GPUs"; "9x 1RU NVLink switch trays" of "2x NVLink NVSwitches" each · NVIDIA System Hardware & Components: 18 compute trays, 9 NVLink switch trays of 2 NVSwitch ASICs each
- A 400G module, e.g.
- NVIDIA single-port 400G OSFP, DR4
SpecSources: NVIDIA specifications: single-port 400G OSFP DR4 transceiver
- Kind
- Mach-Zehnder, a common silicon-photonics modulator design
ReportedSources: Optica (OFC 2019, Th4A.6) abstract: single-lane 200G optical interconnects demonstrated with a silicon photonic Mach-Zehnder modulator (the earlier "commercial mainstream" wording came from a trade newsletter whose link is dead and is not repeated here)
- Core current
- ≈1,300 A
Calc.Calculated: Current = GPU power less its HBM share (the HBM stacks have their own supply) ÷ an assumed 0.8 V core voltage. Method
- Efficiency
- ≈91%
AssumedAssumed: Voltage-regulator (VRM) efficiency, 90–92%. Why
- Loss, campus-wide
- ≈5.4 MW
Calc.Calculated: Per-rack loss = power passing through the stage × (1 ÷ assumed stage efficiency − 1); the campus figure sums this across every rack the scenario builds. Method
- GPU dies, whole campus
- 47 MW
Calc.Calculated: Per GPU, the package power less its HBM share; for the campus, that times the GPU count, and as a share, that over the meter MW. The ledger’s rows, this, and the unallocated remainder add up to the meter power. It covers everything on the compute dies (computation, on-chip memory, communication, control and leakage); the model does not estimate the part that is useful arithmetic. Method
- Share of the meter
- 47%
Calc.Calculated: Per GPU, the package power less its HBM share; for the campus, that times the GPU count, and as a share, that over the meter MW. The ledger’s rows, this, and the unallocated remainder add up to the meter power. It covers everything on the compute dies (computation, on-chip memory, communication, control and leakage); the model does not estimate the part that is useful arithmetic. Method
- Bandwidth
- 8 TB/s
SpecSources: NVIDIA specifications: "372 GB" HBM3e and "16 TB/s" per Grace Blackwell Superchip (2 GPUs) · Micron specifications table: 24 GB at 8-Hi, >1.2 TB/s per stack
- Tokens a second, campus
- 54.3 million
Calc.Calculated: Tokens a second = GPUs × tokens a second per GPU × utilization, from the calculator’s settings. The per-GPU rate defaults to a figure scaled from each accelerator’s HBM bandwidth until the reader sets one. Method
Assumed: Default tokens a second per GPU, 2,000 for an 8 TB/s GPU, scaled with HBM bandwidth. Why
- Tokens per kWh at the meter
- 1.8 million
Calc.Calculated: Joules per token = meter W ÷ tokens a second, plus, when the calculator includes it, a share of training: training energy ÷ the tokens the model serves over its life. Tokens per kWh = 3.6 million J ÷ joules per token. Method
- Meter power
- 100 MW
AssumedAssumed: Modeled campus size, set by the reader. Why
- This step, per watt at the meter
- 0.007 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.059 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- PUE, this design
- 1.14
Calc.Calculated: IT MW solves meter MW × upstream efficiency = IT MW ÷ IT-path efficiency + (cooling fraction + misc fraction) × IT MW ÷ side-path efficiency, chaining the model’s own conversion efficiencies; PUE = meter MW ÷ IT MW. Method
- This step, per watt at the meter
- 0.058 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.050 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.023 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.067 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.125 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.068 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- This step, per watt at the meter
- 0.072 W
Calc.Calculated: Each step’s slice = the ledger rows for that step ÷ meter MW: the main transformers and campus cables; cooling and lighting; the power room; the network switches and optics; rack power; the NVLink switches; host CPUs, NICs and drives; converters and regulators; memory. What is left reaches the GPU dies. The unallocated remainder, never drawn, gets no step of its own. Method
- Reaches the GPU dies, per watt
- 0.472 W
Calc.Calculated: Per GPU, the package power less its HBM share; for the campus, that times the GPU count, and as a share, that over the meter MW. The ledger’s rows, this, and the unallocated remainder add up to the meter power. It covers everything on the compute dies (computation, on-chip memory, communication, control and leakage); the model does not estimate the part that is useful arithmetic. Method
- Timing
- illustrative, the same for every GPU
AssumedAssumed: An illustrative request timeline, internet ≈25 ms each way, fiber vault 1 ms, queue 50 ms, front-end network 0.2 ms, prefill 200 ms, 60 tokens a second per stream, a 500-token reply. Why
- Speed in fiber
- ≈4.9 µs per km, one way
Calc.Calculated: Speed = speed of light ÷ silica fiber’s group refractive index (≈1.47) ≈ 2.04×10⁸ m/s, which is ≈4.9 µs per kilometer, one way. Method
- Routes
- 2 or more, physically separate
ReportedSources: TRG Datacenters "A properly designed facility has dual fiber entrances. Fiber enters from two separate locations, following different physical paths into the building."
- A serving copy, this tour
- one rack, 72 GPUs
AssumedAssumed: One serving copy per NVLink domain, one NVL72 rack (72 GPUs), or one 8-GPU server for H100. Why
- Timing
- illustrative, the same for every GPU
AssumedAssumed: An illustrative request timeline, internet ≈25 ms each way, fiber vault 1 ms, queue 50 ms, front-end network 0.2 ms, prefill 200 ms, 60 tokens a second per stream, a 500-token reply. Why
- Traffic
- every layer, many times per token
ReportedSources: Meta AI, arXiv describes tensor-parallel GPUs exchanging activations inside every transformer layer, many times per forward/backward pass
- NVLink per GPU
- 1.8 TB/s
SpecSources: NVIDIA Blackwell platform launch release: "the latest iteration of NVIDIA NVLink delivers groundbreaking 1.8TB/s bidirectional throughput per GPU" (the NVL72 product page itself states only the 130 TB/s system aggregate, not a per-GPU figure)
- DPUs per tray
- 2
SpecSources: NVIDIA Compute tray includes two BlueField-3 DPUs.
- Timing
- illustrative, the same for every GPU
AssumedAssumed: An illustrative request timeline, internet ≈25 ms each way, fiber vault 1 ms, queue 50 ms, front-end network 0.2 ms, prefill 200 ms, 60 tokens a second per stream, a 500-token reply. Why
- Prefill, this example
- 200 ms
AssumedAssumed: An illustrative request timeline, internet ≈25 ms each way, fiber vault 1 ms, queue 50 ms, front-end network 0.2 ms, prefill 200 ms, 60 tokens a second per stream, a 500-token reply. Why
- Time to first token, this example
- ≈301 ms
Calc.Calculated: The sum of the illustrative steps before the first word is back on the phone: the internet in (25 ms), the fiber vault (1 ms), the queue (50 ms), the front-end network (0.2 ms), prefill (200 ms) and the internet back (25 ms). Method
- Stream rate and reply length
- 60 tokens/s, 500 tokens
AssumedAssumed: An illustrative request timeline, internet ≈25 ms each way, fiber vault 1 ms, queue 50 ms, front-end network 0.2 ms, prefill 200 ms, 60 tokens a second per stream, a 500-token reply. Why
- Energy per reply, at the meter
- ≈0.28 Wh, training share included
Calc.Calculated: Wh per reply = joules per token × 500 tokens ÷ 3,600. That is meter energy, cooling included; the IT equipment’s part is that ÷ PUE. Method
- Bandwidth
- 8 TB/s
SpecSources: NVIDIA specifications: "372 GB" HBM3e and "16 TB/s" per Grace Blackwell Superchip (2 GPUs) · Micron specifications table: 24 GB at 8-Hi, >1.2 TB/s per stack
- Energy per reply, at the meter
- ≈0.28 Wh, training share included
Calc.Calculated: Wh per reply = joules per token × 500 tokens ÷ 3,600. That is meter energy, cooling included; the IT equipment’s part is that ÷ PUE. Method
- IT energy per reply
- ≈0.25 Wh
Calc.Calculated: Wh per reply = joules per token × 500 tokens ÷ 3,600. That is meter energy, cooling included; the IT equipment’s part is that ÷ PUE. Method
- Water on site, per reply
- ≈0.039 mL
Calc.Calculated: mL = the reply’s IT energy in Wh × WUE in liters per kWh of IT energy (Wh × L/kWh = mL). WUE is defined on IT energy, so the meter figure is divided by PUE first. Method
Assumed: Water use by cooling design, air 1.0, liquid 0.5, warm water 0.16 L/kWh IT. Why
- Compute dies, this model
- ≈1,042 W
Calc.Calculated: Per GPU, the package power less its HBM share; for the campus, that times the GPU count, and as a share, that over the meter MW. The ledger’s rows, this, and the unallocated remainder add up to the meter power. It covers everything on the compute dies (computation, on-chip memory, communication, control and leakage); the model does not estimate the part that is useful arithmetic. Method
- Die area, two dies
- ≈16 cm²
ReportedSources: WCCFTech body text: "AI Superchip - 208 Billion Transistors (TSMC 4NP, >1600mm2)"
- Average flux
- ≈65 W/cm²
Calc.Calculated: Flux = GPU power less its HBM share ÷ die area. Hot spots run well above this average. Method
- Die, this operating point
- ≈75 °C
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- Layers to coolant
- die, interface, lid, interface, cold plate
AssumedAssumed: Layers between die and coolant, die → thermal interface → lid → thermal interface → cold plate or heat sink; H100: no lid. Why
- Lid, this operating point
- ≈67 °C
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- NVIDIA warm-water spec
- 45 °C in, ≈55 °C out
SpecSources: NVIDIA NVIDIA blog: "the coolant entering a fully liquid-cooled chip at 45 degrees Celsius exits at roughly 55 degrees"
- To liquid, this model
- ≈114 kW
Calc.Calculated: Split the rack total by the liquid-cooled share this site assumes for this rack (the cited vendor spec sheet could not be re-read in the 10/08/2026 audit). Method
- Rise across the rack
- ≈10 °C
ReportedSources: Alliance Chemical "roughly 170–195 liters per minute of coolant at a 10°C inlet-to-outlet rise (about 1.5 LPM per kW)" for a GB200 NVL72 rack
- Supply → return, this design
- ≈45 → 55 °C
SpecSources: NVIDIA NVIDIA blog: "the coolant entering a fully liquid-cooled chip at 45 degrees Celsius exits at roughly 55 degrees"
- Approach, facility to rack loop
- a few °C (≈3 °C here)
AssumedAssumed: CDU approach temperature, facility to rack loop, a few °C (≈3 °C in this model). Why
- Facility water, supply → return
- 42 → 52 °C
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- Carries
- nearly all of the hall’s heat
AssumedAssumed: Standard switchgear, battery and busway design practice, automatic utility/generator transfer; Li-ion (LFP or NMC) UPS batteries; tap-off busway. Why
- Facility water return
- ≈52 °C
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- Heat rejected
- ≈92 MW
Calc.Calculated: Heat rejected ≈ IT MW × 1.05, adding back the plant’s own electrical overhead as heat. Method
- Facility water supply, back to the hall
- ≈42 °C
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- Sprays needed above
- ≈35 °C outside
AssumedAssumed: One operating point for the cooling loops, rack loop +10 °C across a rack; the CDU ≈3 °C apart on each side; die ≈20 °C above the coolant leaving its plate; chiller-made water 12 °C (air) or 20 °C (liquid); supply air 22 °C with an 18 °C rise (air); condenser water 35 °C; a 35 °C design afternoon. Why
- Heat out
- 100 MW
Calc.Calculated: Heat out ≈ meter MW: energy conservation means virtually every watt drawn eventually becomes heat. Method