What GPU do I need to run RedHatAI/DeepSeek-R1-Distill-Llama-70B-FP8-dynamic?

70.6B parameters, published in F8_E4M3. View on Hugging Face

70.6B
Parameters
F8_E4M3
Native precision
LlamaForCausalLM
Architecture
text-generation
Pipeline

DeepSeek-R1-Distill-Llama-70B-FP8-dynamic is published by RedHatAI on Hugging Face, with 14,681 downloads and 10 likes to date. It's a LlamaForCausalLM model built for text-generation, published natively in F8_E4M3. Its name carries the distilled tag.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP8 (native)65.7 GB78.9 GBRTX PRO 6000 WS1$1.62/hr
cheaper alt.RTX 4000 SFF Ada4$0.792/hr
INT4 (quantized)32.9 GB39.4 GBRTX A60001$0.363/hr
cheaper alt.RTX A50002$0.352/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run DeepSeek-R1-Distill-Llama-70B-FP8-dynamic at its published (F8_E4M3) precision: 1× RTX PRO 6000 WS, at $1.62/hr per GPU ($1.62/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

DeepSeek-R1-Distill-Llama-70B-FP8-dynamic: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 327,680 bytes at 16-bit.

ContextKV cache, one sequence
4K1.3 GB
32K10.0 GB
128K40.0 GB

Computed from the layer, head and window counts in the model's own configuration (RedHatAI/DeepSeek-R1-Distill-Llama-70B-FP8-dynamic), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

DeepSeek-R1-Distill-Llama-70B-FP8-dynamic: common questions

Can DeepSeek-R1-Distill-Llama-70B-FP8-dynamic run on a single GPU?

Yes, but not on a desktop card. At FP8 (native) it needs 78.9 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 96.0 GB RTX PRO 6000 WS at $1.62/hr.

Is DeepSeek-R1-Distill-Llama-70B-FP8-dynamic already quantized?

Yes. It is published in FP8, one byte per parameter, so the 78.9 GB figure is already a quantized footprint rather than a full-precision one. Only INT4 goes below it, at 39.4 GB. A GPU without FP8 tensor cores cannot run it as published, which is why cards here are matched on precision support and not on VRAM alone.

Does quantizing DeepSeek-R1-Distill-Llama-70B-FP8-dynamic lower the GPU bill?

Yes. At FP8 (native) the cheapest live fit is one RTX PRO 6000 WS at $1.62/hr. At INT4 (quantized) it drops to one RTX A6000 at $0.363/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More DeepSeek R1 models

All 13 DeepSeek R1 models: VRAM and GPU requirements

Lineage

Based on DeepSeek-R1-Distill-Llama-70B.

Alternatives at this size

Other models for text-generation within about a third of DeepSeek-R1-Distill-Llama-70B-FP8-dynamic's 70.6B parameters, from other model lines.

More on DeepSeek-R1-Distill-Llama-70B-FP8-dynamic

Related reading: RTX PRO 6000 WS pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.