All compatibility checks

Compatibility check

Can you run DeepSeek R1 Distill Qwen 32B on the H200 141GB?

Yes — runs in full precision

Yes. DeepSeek R1 Distill Qwen 32B fits on the H200 141GB (141 GB) in full FP16/BF16 precision, using about 76.3 GB including a 1 GB KV cache at 4,096 tokens. You have comfortable headroom for longer prompts and modest batching.

Memory breakdown

Weights plus a 1 GB KV cache at 4,096tokens, against the card's 141 GB. Verdicts leave ~10% headroom for activations and fragmentation.

PrecisionWeightsKV cacheTotal% of 141 GBFit
FP16 / BF16full quality75.3 GB1 GB76.3 GB54%Fits
INT8 (8-bit)near-full quality37.7 GB1 GB38.7 GB27%Fits
INT4 (4-bit)GPTQ / AWQ / GGUF Q418.8 GB1 GB19.8 GB14%Fits

Planning estimates, not a substitute for profiling. Real usage varies with the inference runtime, batch size, and how much context you actually use — the KV cache grows linearly with prompt length.

GPUs that run DeepSeek R1 Distill Qwen 32B

Cards where this model fits (at its best precision):

Go deeper

Frequently asked questions

Can the H200 141GB run DeepSeek R1 Distill Qwen 32B?

Yes. In FP16 it uses about 76.3 GB, which fits the H200 141GB's 141 GB.

How much VRAM does DeepSeek R1 Distill Qwen 32B need?

Approximately 75.3 GB in FP16, 37.7 GB in INT8, and 18.8 GB in 4-bit for the weights, plus a KV cache of about 1 GB at 4,096 tokens.

Does quantization let DeepSeek R1 Distill Qwen 32B fit on the H200 141GB?

Yes. Dropping to FP16 / BF16 brings total usage to about 76.3 GB, which fits the 141 GB card with headroom for the KV cache.

What happens to memory with longer context?

The KV cache grows linearly with prompt length. At 4,096 tokens it is about 1 GB here; doubling the context roughly doubles that term, so long-context use can push a tight fit over the edge.