Can the RTX A6000 48GB Run DeepSeek-R1-Distill-Qwen 32B?
Runs
Yes. DeepSeek-R1-Distill-Qwen 32B at Q4_K_M is a 19.9 GB download (Hugging Face file listing for bartowski/DeepSeek-R1-Distill-Qwen-32B-GGUF), and the RTX A6000 48GB has 48 GB of VRAM, leaving about 28.2 GB for the KV cache and runtime. Published runs put generation at a median of 26.2 tokens per second across 1 cited measurement. Fastest cited run: DatabaseMart.
Buy the RTX A6000 48GB
No new listing for this card is tracked on Amazon today; it mostly trades used.
Published runs for DeepSeek-R1-Distill-Qwen 32B on the RTX A6000 48GB
| Generation | Quant | Runtime | Context | Source | Date |
|---|---|---|---|---|---|
| 26.2 tok/s | q4_0 | ollama | — | DatabaseMartlabelled "deepseek-r1:32b" | 2025-02-01 |
More about this pair
How much VRAM does DeepSeek-R1-Distill-Qwen 32B need?
The Q4_K_M file is 19.9 GB. Add roughly 1.5 GB for the runtime and an ~8K-token context, so about 21.4 GB of VRAM holds it comfortably. Longer contexts grow the KV cache and need more.
What is the fastest DeepSeek-R1-Distill-Qwen 32B can generate on the RTX A6000 48GB?
Generation reads every weight once per token, so the RTX A6000 48GB's 768 GB/s of memory bandwidth divided by the 19.9 GB file sets a ceiling near 39 tokens per second. Real runs land below it; SpecPicks rejects any published figure above it.
Check another pair
DeepSeek-R1-Distill-Qwen 32B on other GPUs
- RTX 4060 — Offload
- RTX 3060 Ti — Offload
- RTX 3060 12GB — Offload
- Intel Arc B580 — Offload
- RTX 4070 SUPER — Offload
- RTX 4060 Ti 16GB — Offload
- RTX 5060 Ti 16GB — Offload
- Intel Arc A770 16GB — Offload
- Radeon RX 9070 XT — Offload
- RTX 4070 Ti SUPER — Offload
- RTX 4080 — Offload
- RTX 5070 Ti — Offload
- RTX 5080 — Offload
- RTX 3090 — Runs
- Radeon RX 7900 XTX — Runs, 26 tok/s median
- RTX 4090 — Runs, 34.2 tok/s median
- RTX 5090 — Runs, 49.8 tok/s median
- RTX PRO 6000 Blackwell 96GB — Runs, 64.3 tok/s median
Other models on the RTX A6000 48GB
- Llama 3.2 1B — Runs
- Llama 3.2 3B — Runs
- Mistral 7B — Runs
- Qwen2.5 7B — Runs
- Llama 3.1 8B — Runs
- DeepSeek-R1-Distill-Llama 8B — Runs
- Qwen3 8B — Runs
- Gemma 2 9B — Runs
- Gemma 3 12B — Runs
- Qwen2.5 14B — Runs, 50.3 tok/s median
- DeepSeek-R1-Distill-Qwen 14B — Runs, 48.4 tok/s median
- Qwen3 14B — Runs, 40.7 tok/s median
- Phi-4 14B — Runs, 52.6 tok/s median
- gpt-oss-20b — Runs
- Gemma 3 27B — Runs
- Gemma 2 27B — Runs, 31.6 tok/s median
- Qwen3 30B-A3B — Runs
- Qwen3 32B — Runs, 27.5 tok/s median
- Qwen2.5 32B — Runs, 26.1 tok/s median
- Llama 3.1 70B — Runs, 14.6 tok/s median
- Llama 3.3 70B — Runs, 13.6 tok/s median
- DeepSeek-R1-Distill-Llama 70B — Runs, 13.9 tok/s median
How the checks work
The fit is the Q4_K_M file size against the card's VRAM, with 1.5 GB kept for the runtime and an ~8K context. A published run counts only if the pair fits, the run is Q4-class, its source does not call it an estimate, it is under the bandwidth ceiling above, and it is not one figure pasted across many cards. The whole matrix is downloadable as a CSV under CC BY 4.0.
As an Amazon Associate, SpecPicks earns from qualifying purchases.
This page is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.