BLOG · COMPARISON · JUNE 2026

H200 NVL vs H100 NVL: when the premium pays off

IN BRIEF
  • Compute specs are identical at every precision, from FP64 to INT8
  • H200 NVL carries 1.5× the memory (141 vs 94 GB) and 1.22× the bandwidth (4,813 vs 3,938 GB/s)
  • Real-task gains range from 0% to 3.4×: zero on short context in BF16, 3.4× on 32K-token inputs
  • MLPerf at equal 700 W shows +28% on Llama 2 70B, not the headline 90%
  • H200 NVL bridges up to four cards (564 GB); H100 NVL only two (188 GB)

First, the fact that breaks most comparisons

Put the two spec sheets side by side and you will see something reviews rarely mention: the compute sections match to the last digit. Not approximately: exactly.

PRECISIONH200 NVLH100 NVL
FP6430 TFLOPS30 TFLOPS
FP3260 TFLOPS60 TFLOPS
TF32 Tensor Core835 TFLOPS835 TFLOPS
BF16 / FP16 Tensor Core1,671 TFLOPS1,671 TFLOPS
FP8 / INT8 Tensor Core3,341 TFLOPS3,341 TFLOPS
Boost clock1,785 MHz1,785 MHz

Tensor figures with structured sparsity, per NVIDIA’s own footnotes

The consequence is simple: if your task is compute-bound, the two cards perform the same on paper. One caveat an engineer will raise: the H100 NVL defaults to a 400 W cap and the H200 NVL to 600 W, so under sustained load the older card can clock down earlier; identical peak specs are a spec-sheet statement, not a measured one. That said, NVIDIA’s own MLPerf report states that after TensorRT-LLM optimisations, Llama 2 70B on H200 is limited by compute, not memory bandwidth.

All the difference lives in memory

PARAMETERH200 NVLH100 NVL
Capacity141 GB94 GB
TypeHBM3eHBM3
Bandwidth4,813 GB/s3,938 GB/s
Memory clock3,201 MHz2,619 MHz
Bus width6,016-bit6,016-bit
MIG profilesup to 7 × 1g.18gb (16.5 GB usable each)up to 7 × 1g.12gb

Both NVL cards run a wider bus than the H100 SXM: six HBM stacks instead of five, so even the older H100 NVL delivers 3.9 TB/s against 3.35 on SXM. Why the capacity is 94 GB rather than a round 96, NVIDIA explains nowhere.

What it buys on specific workloads

There is no single number. The spread runs from zero to 3.4×, depending on how memory-bound the task is.

SCENARIOGAINWHO MEASURED
Short context, 128 tokens, BF16~0%Baseten
Same in FP8+11%Baseten
Llama 2 70B, equal 700 W+28%MLPerf
Batch 4096, FP8+36%Baseten
Batch 4096, BF16+47%Baseten
HPC application suite (NVL claim)up to 1.3×NVIDIA
32,768-token input, batch 643.4×Baseten

Baseten and MLPerf measured SXM cards (8×H200 vs 8×H100, 700 W); the NVL cards run 600 W against 400 W, so treat the ratios as indicative

Baseten’s conclusion is blunter than any slogan: outside these situations, H200 gives a minimal gain over H100, and many inference workloads are more cost-effective on H100. For the NVL pair NVIDIA itself promises up to 1.7× on language models and 1.3× on HPC, without publishing the test conditions.

How to read the presentation numbers

The loudest figure in H200 materials is “110× on HPC”. The footnote reveals the baseline: four GPUs against a pair of Sapphire Rapids 8480 CPUs. It is a comparison with processors, not with H100.

The second figure is 1.9× on Llama 2 70B. NVIDIA’s footnote shows the conditions: H100 ran batch 8, H200 ran batch 32. That is not cheating: the bigger batch is possible precisely because of the bigger memory, the KV-cache arithmetic, and that is the point of the product. But it does not mean the same workload runs twice as fast. If your model already fits in 94 GB with the batch you need, that gain will not appear.

NVLink: the biggest generational difference

PARAMETERH200 NVLH100 NVL
Cards per bridge groupup to 4only 2
Group memory564 GB188 GB
NVLink bandwidth900 GB/s600 GB/s
Bridges per card1 wide (separate SKUs for 2- and 4-card)3 narrow, same as A100 PCIe

Bridges of the two generations are not interchangeable

The rated 900 GB/s counts both directions: 18 links at 25 GB/s per direction, 450 GB/s one-way. A documented two-card H200 NVL setup in an HPE DL385 Gen11 shows all 18 links active, reported by nvidia-smi at the raw lane rate of 26.6 GB/s each. Cards outside a bridge group talk over PCIe Gen5 at 128 GB/s, roughly seven times slower.

What changes besides speed

PARAMETERH200 NVLH100 NVL
Default power600 W400 W
Operating ambient10–45 °C0–50 °C
Minimum driverR565 TRD1, CUDA 12.7R535, CUDA 12.2
UEFIsupportednot supported
NVIDIA AI Enterprise5 years included5 years included

Note the second row: the newer card draws 200 W more and tolerates a narrower temperature window on both ends. In a machine room, a detail; in an office server room that heats past 45 °C in summer, a reason not to buy. And the electricity: 200 W of difference around the clock is 1,752 kWh per card per year; the rack maths feels it before the invoice does.

When the premium pays, and when H100 NVL is enough

The rule is one line: the premium is justified when the gain on your workload profile, in percent, exceeds the price difference in percent. A chat service with short prompts and an 11% gain on a card that costs 40% more makes every token more expensive. Batch-processing 30K-token documents with a 3.4× gain repays the premium in months.

The second calculation matters more, and almost nobody does it: compare configurations, not cards.

MEMORY NEEDED (MODEL + KV CACHE)WHAT IT MEANS IN PRACTICE
up to 94 GBone H100 NVL: the premium buys memory you will not use
94–141 GBone H200 NVL, or a bridged H100 NVL pair. One card = one slot instead of two, 600 W instead of 800
141–188 GBa bridged H100 NVL pair gives 188 GB
over 188 GBH200 NVL only: a pair gives 282 GB, a quad 564 GB. H100 NVL groups beyond two cards do not exist

On buying versus renting: the cloud wins on spiky, one-off workloads. But both NVL cards ship with a five-year NVIDIA AI Enterprise licence (bought separately for SXM), the data stays inside your perimeter; for medical, financial and public-sector projects that is a question of admission, not money, and Hopper is winding down: some server platforms with these GPUs have already closed ordering.

What we supply

Eurokommerz supplies the NVIDIA H200 NVL (141 GB HBM3e, PCIe) and the H100 NVL (both available to order, along with the RTX PRO 6000 Blackwell Server Edition when 96 GB of GDDR7 is enough and HBM is overkill), across the EU, with manufacturer warranty and EU invoicing.

FAQ

Does the H100 NVL work as a single 94 GB card, without a bridge?
Yes. The question comes up constantly because the card was long shown only in 188 GB pairs; ServeTheHome even published a dedicated clarification.
Will an H100 NVL bridge fit the H200 NVL?
No. H100 NVL uses three narrow bridges (same as A100 PCIe); H200 NVL uses one wide bridge of a new type with separate SKUs for two- and four-card groups. Plan new bridges when upgrading the fleet.
Does vGPU via mdev work on the H200?
No, and that is expected: like every Ampere-and-later data-centre GPU, the H200 exposes vGPU only through SR-IOV, so there are no mdev_bus directories. The real blocker on Proxmox VE is different: NVIDIA states on its forum that Proxmox-based KVM is not yet a supported NVIDIA AI Enterprise platform.
Do two servers with H200 NVL need an InfiniBand switch?
NVIDIA answered this directly on its forum: no. Connect the ConnectX-7 adapters back-to-back. The real trap is NUMA: if the GPU and the NIC sit in different nodes, traffic routes through the CPU.
Does NVLink work inside a virtual machine?
There is a documented case: two H200 NVL in HPE DL385 Gen11, Proxmox VE 8.4, VFIO passthrough, Ubuntu guest; all 18 links active inside the VM. Working, but outside any officially guaranteed scenario.

Tell us the model, the context length and how many concurrent requests you plan. We will calculate the memory footprint, say whether one card or a bridged group is needed, and check compatibility with your platform. We reply within one business day.

Talk to an expert
Talk to an expert

We reply within one business day

By sending this form you agree that we process your details to answer your enquiry – see our privacy policy.

request@eurokommerz.at  ·  +43 1 585 1405 50  ·  Jordangasse 7, 1010 Vienna