NVIDIA GB300 NVL72 rack (72 Blackwell Ultra GPUs): fully liquid-cooled, Max TDP up to 1,400 W per GPU
Fields
supply/gb300-nvl72-rack-1400w-per-gpuNotes
The high-water mark for a single accelerator's power envelope in any shipping NVIDIA rack. Technical Specifications table: GB300 NVL72 per-Blackwell-Ultra-GPU Max TDP is 'Configurable up to 1,400 W'; the 8-GPU HGX B300 sibling is 'Configurable up to 1,100 W'. The generation ladder from datasheets in this repo: H100 SXM 700 W, H100 PCIe 350 W, HGX B200 up to 1,000 W, HGX B300 up to 1,100 W, GB200 NVL72/NVL4 up to 1,200 W, GB300 NVL72 up to 1,400 W - roughly 2x Hopper per GPU in two generations, with a notably non-monotonic ordering between B200 (1000 W) and GB200 NVL72 (1200 W) that reflects rack context rather than silicon. COOLING IS EXPLICIT AND TOTAL: 'The NVIDIA GB300 NVL72 features a fully liquid-cooled, rack-scale architecture that integrates 72 NVIDIA Blackwell Ultra GPUs and 36 Arm-based NVIDIA Grace CPUs into a single platform'. This is the generation where liquid stops being partial (GB200 liquid-cooled CPUs and GPUs via cold plates but air-cooled networking and storage) and becomes the rack's defining characteristic. THE MOST IMPORTANT NUMBER ON THIS PAGE IS NOT THE WATTAGE - IT IS THE DENOMINATOR. NVIDIA's own performance charts for both GB300 NVL72 and HGX B300 normalize throughput to 'Tokens per Second (TPS) in 1 MW (Throughput)' - the vendor is now selling tokens per megawatt of facility power rather than tokens per GPU. That is the clearest possible vendor admission that at this density power is the binding unit of account and compute is not. Practical consequence: a 1,400 W per-GPU ceiling with 72 GPUs implies a rack envelope in the same neighbourhood as GB200 NVL72 (the exact GB300 rack power figure is NOT published in the datasheet - do not infer one), so a facility that cannot take GB200 cannot take GB300 either. Rack power for GB300 is recorded as unknown rather than extrapolated.
EXPORT CONTROL (2026-10-04, mechanism-level; sources spl-eccn-3a090-ccl, spl-bis-2026-01-advanced-computing-case-by-case, spl-bis-2026-05-d5-guidance): these parts classify under ECCN 3A090.a/.b, whose thresholds are 'total processing performance' (TPP) >= 4800, or TPP >= 1600 with performance density >= 5.92 (the .b band is TPP 2400-4800 with performance density 1.6-5.92, or TPP >= 1600 with performance density 3.2-5.92). The mechanism has THREE layers and all three must be cleared, not just one: (a) LICENSE FOR EXPORT FROM THE US - controlled by the January 2026 rule (91 FR 1684, effective 2026-01-15), which moved TPP < 21,000 AND total DRAM bandwidth < 6,500 GB/s parts from presumption of denial to CASE-BY-CASE REVIEW, but only for exports from the US to end users in China/Macau, and only against six exporter certifications - US supply sufficiency judged 'taking into account normal lead times', no diversion of foundry capacity away from US end users, aggregate China+Macau shipments capped at 50% of US end-use shipments, no end-user prohibition, consignee KYC procedures, and prior verification by a qualified third-party US testing lab of TPP, total DRAM bandwidth, interconnect bandwidth and copackaged DRAM capacity; (b) END-USER AND PARENT-COMPANY SCREENING under 742.6(a)(6)(iii)(A) - per BIS guidance of 2026-05-31 a licence is required where the consignee is HEADQUARTERED in Country Group D:5 or Macau OR ITS ULTIMATE PARENT is so headquartered, EVEN IF the consignee itself is outside D:5/Macau, which means the destination country alone never answers the question; (c) THE LIMITS THAT REMAIN - reexports and in-country transfers of the same chips to China/Macau remain PRESUMPTION OF DENIAL, and exports to D:5/Macau-headquartered or -parented entities remain presumption of denial wherever the buyer sits. The Jan-2025 AI Diffusion Rule was rescinded and not enforced from 2025-05-13, but that rescission did not remove (a) or (b). THE OUTCOME THAT DECIDES A PROCUREMENT (source spl-nvda-10q-fy2027q2-h200-licence-outcome): a licence is necessary but demonstrably NOT sufficient. NVIDIA has been granted H200 licences under exactly this regime and reported that those sales were 'restricted by the PRC government', that it made 'a fraction of the allowed shipments', and that both those shipments and all Data Center Hopper shipments to China in the quarter were LESS THAN 1% of Data Center revenue - alongside a $0.4 billion H200 excess-inventory and purchase-obligation charge. The licences additionally require US inspection before shipment, which attracts a 25% tariff on importation into the US that NVIDIA states it cannot pass on. So a destination-market import approval, not the US licence, was the binding constraint.
LEAD TIME: null - and for this record that is the WRONG QUESTION, which is the point worth recording. This record measures a build constraint that is not the accelerator supply chain: the lead time for a 120 kW liquid-cooled rack is set by construction, electrical service, and CDU/manifold plumbing, not by GPU allocation. Its own notes already make this argument for the colo case, so this entry only fixes the boundary: do not read a GPU lead time into a facility lead time, and do not read a facility lead time into a GPU lead time. No vendor publishes a weeks figure for either, so both stay null - probe log in source spl-negative-no-oem-publishes-lead-time. Where a real published horizon exists for the supply side it is on the accelerator record (NVIDIA's $95.2bn purchase and supply/capacity obligations substantially payable through FY2027, source spl-nvda-10k-fy2026-supply-commitments).