LEVIATHAN SYSTEMS
GPU Deployment Services

NVIDIA GPU Platform Comparison: H100, H200, GH200, GB200, and GB300 for Data Center Deployment

Leviathan SystemsPublished 2026-02-075 min read
TL;DR

Compare the delivered system, not just the GPU name

A platform shortlist becomes a physical deployment decision only when each option identifies the delivered unit, population, power boundary, liquid and air heat paths, external network interfaces and remaining work. A GPU board, a CPU–GPU superchip, a complete server and a rack-scale system are different comparison units.

Choosing the Right NVIDIA GPU Platform

This comparison uses public specifications checked on October 20, 2026, with dated source issues identified below. It retains the five platform families because they present different physical questions, not because they can be ranked on one complexity or performance scale. Current product-page figures must not be mixed with an older announcement or a different OEM configuration.

First establish what the supplier actually proposes to deliver: GPU modules or cards in a named server, a Grace Hopper implementation, or an integrated NVL72 rack and its external interfaces. Then compare the complete installation package. Workload selection and benchmark interpretation are covered in the GPU performance comparison guide; the GB300 architecture guide explains that platform in more detail. Here the decision is what those choices change in the physical buying and handoff package.

Named Variants and Their Deployment Boundaries

NVIDIA H100

H100 names a Hopper GPU family, not a server form factor. The current NVIDIA specifications distinguish an 80 GB SXM implementation from 94 GB H100 NVL, with different power limits and interfaces. Identify the actual GPU variant and complete OEM system before interpreting an H100 line in an equipment list.

The current table lists H100 SXM up to 700 W and H100 NVL at 350–400 W, configurable. The separate H100 PCIe product brief, internally labelled PB-11133-001_v02, November 2022, lists 80 GB HBM2e and a maximum 350 W board-power specification. That older 80 GB PCIe card is not the 94 GB NVL variant or the 700 W SXM configuration. Preserve the exact source and variant instead of assigning one memory type and power value to every H100.

The complete server adds CPUs, host memory, storage, networking, power conversion and cooling components. Its chassis, mass, mounting and airflow requirements come from that system's applicable documents. A GPU specification alone cannot establish a universal 30–40 kW air-cooled rack limit, a suitable PDU or that a location has no special requirements.

NVIDIA H200

H200 remains a Hopper-family product, with a different memory specification. NVIDIA's H200 product table lists 141 GB HBM3e and 4.8 TB/s for both SXM and NVL. Keep that per-GPU capacity distinct from complete-server totals and from the memory figures in a Grace Hopper datasheet.

The same table distinguishes SXM up to 700 W from PCIe-form-factor H200 NVL up to 600 W and lists two- or four-way NVLink bridge support for NVL. The page marks its specifications preliminary and subject to change. Those distinctions matter to the supplier's supported server configuration; NVL is not a universal two-GPU-only package and the family does not have one 700 W requirement.

NVIDIA's November 13, 2023 H200 announcement describes HGX H100 hardware/software compatibility and partner system updates. That supports asking an OEM about an upgrade, not declaring every installed H100 server field-upgradable without changes. Obtain the exact supported upgrade package, retained parts, permitted performing party and affected power, cooling, firmware and support requirements. Compatibility language alone does not authorize replacing modules or release the existing rack position.

NVIDIA GH200 Grace Hopper Superchip

GH200 couples a Grace Arm CPU and Hopper GPU through NVLink-C2C. The March 2025 Grace Hopper datasheet specifies 900 GB/s for the single-superchip CPU-to-GPU interconnect. That is a particular coherent interface, not evidence that every application avoids a CPU/GPU bottleneck or that every x86 server has the same limitation.

The datasheet lists 96 GB HBM3 or 144 GB HBM3e for GH200, alongside its Grace CPU memory. Its configurable 450–1000 W power range covers memory, CPU and GPU together. Do not substitute the H200 table's 141 GB value for this datasheet's 144 GB HBM3e specification, or call the combined superchip figure a GPU-only TDP. Listed capacity also does not establish memory available to a particular application.

A single superchip and GH200 NVL2 are different populations; the datasheet lists separate totals for the two-superchip configuration. The OEM server still defines the delivered chassis, number of superchips, supported adapters, liquid or air solution and external interfaces. A module diagram is not the server's installation package.

For a GH200 proposal, ask the equipment owner to bind the configured server to its applicable documents and distinguish supplied integration from any remaining permitted work. Site handling, structural suitability, cooling interfaces, specialist work and system acceptance remain configuration-specific questions. This comparison supplies no GH200 installation method or evidence that Leviathan has performed a particular deployment.

NVIDIA GB200 NVL72

NVIDIA's GB200 NVL72 specifications identify 36 Grace CPUs and 72 Blackwell GPUs in a rack-scale platform. The published 130 TB/s NVLink figure describes the rack-scale interconnect specification, not a measured application result or the bandwidth of every individual GPU pair.

The current page lists 13.4 TB rack GPU memory and 372 GB for the two-GPU GB200 superchip. It lists NVFP4 Tensor Core performance as 1440 sparse and 720 dense PFLOPS for the rack. Retain precision, sparsity and system population: an unqualified one-exaflop dense claim does not describe that table. Rounded rack memory must not be divided and relabelled as an exact per-device specification.

The DGX GB hardware guide, updated September 17, 2026, describes compute trays, NVLink switch trays, power shelves, an internal bus bar and a passive copper cable-cartridge backplane. It is a named DGX implementation. An integrator's actual delivery package must identify what arrives assembled and the remaining external interfaces; the architecture alone does not prove how a shipment arrives or which tasks are included onsite.

NVIDIA GB300 NVL72

NVIDIA's GB300 NVL72 product page specifies 72 Blackwell Ultra GPUs, 36 Grace CPUs, 20 TB rack GPU memory and 130 TB/s NVLink. Its 1.5× compute comparison is specifically dense FP4 Tensor Core FLOPS relative to Blackwell. It is not a universal training, inference or commissioning speedup.

A shared rack-scale architectural pattern does not fix the supplied power or thermal envelope. Lenovo's GB300 NVL72 guide LP2357, updated August 30, 2026, lists 135 kW TDP and up to 155 kW peak depending on workload and EDP behavior for that offering. These are named product values, not a generic facility allocation or a replacement for the electrical owner's design basis.

Do not assume that a position described as 120 kW-ready for one GB200 package accepts another GB300 package unchanged. Reconcile the exact OEM configurations, power definitions, thermal interfaces, mechanical arrangement, network parts and any supported upgrade documentation. Neither a common NVL72 name nor similar rack dimensions proves compute-tray interchangeability or permission to reuse every retained part.

For GB300 planning, obtain the exact purchased system and its applicable OEM documentation, and distinguish the requested physical work from specialist platform and facility tasks. Leviathan can discuss a separately agreed physical installation package within those boundaries.

Compare the Interfaces Before Comparing Rack Labels

Power: Keep Device Limits and System Input Separate

H100/H200 device limits, GH200's combined memory/CPU/GPU range and an NVL72 rack-power statement use different boundaries. In the DGX reference, power shelves convert facility AC for internal DC distribution through the rack bus bar; the guide describes power whips from a remote panel. An internal bus bar therefore does not establish that every facility must use overhead busway. The responsible supplier and electrical owner must identify the actual input package and applicable requirements.

Fictional EX-POP52 compares Offer A—six complete eight-GPU H100 SXM servers—with Offer B—one 72-GPU NVL72 rack. A contains 6×8=48 GPUs; B contains 72. They are not equivalent populations merely because each offer can be discussed at rack level. Multiplying A's 48 GPUs by the cited up-to 700 W device limit gives 33,600 W of combined GPU limits. That is not complete-server input or a measured load: CPU, host memory, storage, networking, fans and conversion are outside that arithmetic. The buyer still needs the actual complete-system input basis; the calculation supplies no circuit, protection or facility-capacity decision.

Cooling: Account for Liquid and Air Heat Paths

The DGX hardware chapter describes CPU/GPU cold plates and fan-driven air cooling for other components. Liquid-cooled does not mean all heat leaves through liquid. Lenovo's named GB300 offering describes approximately 90% liquid and 10% air heat capture; that ratio is not a universal split for every vendor or operating condition. Its guide also discusses warm-water/economizer operation, so liquid cooling is not synonymous with a mandatory chilled-water plant.

For each actual offer, identify the heat paths, rack-side and facility-side interfaces, environmental conditions and applicable supplier requirements. Appointed cooling and site specialists assess the selected package. An air-cooled server still needs its actual airflow and environmental envelope; neither a modern-data-center label nor the presence of a CDU proves suitability. This comparison provides no fluid choice, flow/temperature setting, filling, testing or connection procedure.

Networking: Count Ports, Channels and Assemblies at Their Own Boundaries

A compute tray, a switch tray, a logical port and a cable assembly are different quantities. The DGX reference's 18 compute trays and 9 NVLink switch trays cannot populate a ports-per-server column. Its internal NVLink backplane and external compute, storage and management interfaces serve different roles. Compare actual endpoint hardware, roles and supported channels; do not convert a tray count or nominal link rate into a cable or optical-trunk quantity.

In EX-POP52, Offer A's server count does not identify its external network population, and Offer B's 72 GPUs do not identify every site cable. Obtain the applicable endpoint and material package, including what is already integrated. At handoff, distinguish physical records, reported inventory/link state and workload evidence. A communication result needs its actual tool release, supported platform, configuration, participants, workload/mode, duration and metrics; a completed cable record cannot supply that result. No order-of-magnitude cable ratio or universal full-bandwidth acceptance follows from the GPU family.

Deployment Timing: Name the Remaining Work and Finish Line

Compare the supplied state and the required outcome: receiving a configured rack, mounting separate complete servers, performing agreed external cabling and obtaining specialist or workload acceptance are different tasks. Each estimate needs its quantity, source issue, input availability, authorized work, resources and receiving owner. A fixed number of assembly or commissioning days per GPU family cannot be derived from the architecture.

For EX-POP52, the buyer can now state the unresolved comparison: 48 versus 72 GPUs, an unprovided complete-system input basis, configuration-specific cooling and an unprovided external connection package. Ask the suppliers and responsible owners to return those items before a like-for-like physical estimate. A later response about rack dimensions alone would answer only that mechanical question; it would not establish power/cooling suitability, supported upgrade work or a comparable delivery schedule.

Connect the Workload Decision to the Physical Package

AI Training at Scale

For training, compare evidence for the intended model, quality target, software and system population. GB300's published dense-FP4 advantage is an arithmetic specification, not a measured training-time ratio. Memory capacity, communication relationships and complete-system scope can make candidates worth evaluating, but they do not establish the fastest accepted job. Use the benchmark companion for that separate workload decision rather than turning the platform name into a recommendation.

AI Inference

For serving, memory fit and response performance are different questions. Identify the variant, model/configuration and actual per-device and distributed memory use, then compare throughput under the required latency and quality conditions. H200 capacity or a GB300 marketing comparison alone cannot establish best value, lowest latency or an approved software deployment for the buyer's workload.

Mixed Workloads and Change Boundaries

A server-based purchase and a rack-scale purchase have different integration and replacement boundaries. Determine what the actual product documentation permits to be added or changed and which shared power, cooling, network or operating dependencies are affected. Removing one server is not automatically independent of its neighbours, and a rack-scale architecture does not prescribe one universal upgrade procedure. The actual owner dispositions and supported package control those decisions.

Costs: Compare the Same Delivered and Accepted Scope

A lower accelerator price or an older generation does not establish the lowest-cost completed workload or deployment. Compare the actual dated offer, equipment population, complete-system requirements, included physical tasks, separate specialist work, support and acceptance scope. Leave an unavailable charge or performance basis unresolved. EX-POP52 is a quantity-and-boundary illustration, not a price, availability, investment-return calculation or recommendation to purchase either offer.

Prepare the Physical Installation Discussion

Leviathan can discuss customer-supplied equipment mounting, rack-and-stack installation, structured cabling, labeling, inspection, remediation and agreed physical checks and handoff records, subject to project scope, site requirements and team availability. Platform/workload selection, facility engineering acceptance and investment-return advice remain with the customer’s appointed qualified owners.

Use the Rack-and-Stack service to discuss the selected equipment's physical package, or the project inquiry to share a nonconfidential outline. Include the exact OEM model/configuration and quantity, supplier delivery state, site and target window, released rack/endpoint inputs, requested mounting/cabling/checks, required handoff and open interfaces. Formal verification or hardware QA requires its own agreed scope, resources and criteria. Liquid-side, facility electrical/structural and specialist handling work, and full software commissioning, remain with their separately appointed responsible parties. No platform eligibility, site acceptance or deployment history is inferred here.

Discuss Your Infrastructure Project_

Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.

Discuss a ProjectEmail Project Scope