Running DeepSeek V4 on H200 SXM server
DeepSeek V4 has 1600 billion parameters. H200 SXM server offers 1,128 GB of HBM3e across 8 GPUs memory. This page puts the two side by side.
How much memory does DeepSeek V4 need?
Weights take the parameter count multiplied by the format size, plus a 15% runtime margin for activations and buffers. The attention cache sits on top: it grows with context length and with the number of concurrent requests, so it is sized case by case.
| Format | Weights in memory | On this machine | What the format costs |
|---|---|---|---|
| FP16 | 3,680 GB | does not fit | full precision, the quality reference |
| FP8 | 1,840 GB | does not fit | negligible loss on most tasks |
| NVFP4 | 920 GB | tight | Blackwell format, native FP4 compute |
| Q4 | 920 GB | tight | block quantisation, broadly supported |
What is left to serve requests?
DeepSeek V4 barely fits on H200 SXM server. In NVFP4, its weights take about 920 GB against 1,128 GB available. The 208 GB margin disappears quickly as context grows. The remaining margin decides how many concurrent requests and how much context the machine sustains. A margin below a quarter of memory forces a limit on context or on concurrency.
H200 SXM server ranges from 350 to 500 k€, indicative and not contractual. The machine targets the GE segment.
Where else can DeepSeek V4 run?
See the DeepSeek V4 and H200 SXM server fact sheets.
How much memory does DeepSeek V4 need?
In NVFP4, weights take about 920 GB including the runtime margin. The attention cache sits on top and depends on context.
Does DeepSeek V4 fit on H200 SXM server?
DeepSeek V4 barely fits on H200 SXM server. In NVFP4, its weights take about 920 GB against 1,128 GB available. The 208 GB margin disappears quickly as context grows.
Method
Parameter counts and memory figures come from the site fact sheets. Memory footprints are calculated, not measured: a reading on real hardware may differ depending on the engine and the exact weight format. Prices are indicative and not contractual.