Won't fitfp16 · 4K ctx · batch 1

Does H200 run Qwen2.5-72B? No at fp16.

At fp16 precision, Qwen2.5-72B (72 B parameters) needs roughly 146.7 GB of VRAM. H200 only has 141 GB, short by 5.7 GB. INT4 quantization brings it down to 44.0 GB — that fits.

104%
VRAM
Won't fit
Estimated VRAM (fp16)
146.7 GB
of 141 GB on H200· 5.7 GB short
Tok/sec
29
TFTT
1756ms
Power
490W
Rent on GPUniq marketplace
H200
Live prices from verified providers · billed hourly, no commitment.
Rent now

Memory breakdown (fp16)

Quantization comparison

Lower precision = less VRAM with a small quality trade-off. Quality order: FP16 > INT8 > INT4.

PrecisionVRAMUtilisationFits on H200?
FP16 (full precision)146.7 GB104%Won't fit
INT8 (8-bit)78.3 GB55%Runs well
INT4 / Q4 (4-bit)44.0 GB31%Runs easily

Frequently asked

Can H200 run Qwen2.5-72B?
Not at fp16 — Qwen2.5-72B needs about 146.7 GB while H200 has 141 GB. It fits at INT4 quantization (44.0 GB) with some accuracy trade-off.
How much VRAM does Qwen2.5-72B use?
About 146.7 GB at fp16, 44.0 GB at INT4 (for a 4K context, batch size 1). Longer contexts add to KV cache size; larger batches increase activations.
What's the fastest way to run Qwen2.5-72B on H200?
Use a production inference engine like vLLM, SGLang, or TensorRT-LLM with paged attention — they cut KV cache 2–3× vs the naive estimate and batch multiple requests efficiently. For H200, enable Flash Attention 2.
Where can I rent a H200?
GPUniq aggregates live H200 offers from verified providers. You can deploy an instance in about a minute and pay hourly with no commitment.
Try it live

Chat with Qwen2.5-72B — no setup

Send a prompt and see how Qwen2.5-72B responds directly in our chat. No installation, no GPU required to test.

Open in chat
Want to tweak sequence length, batch size, or fine-tuning? Open the full calculator →