DeepSeek-R1-0528-Qwen3-8B GGUF size and VRAM requirements
MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF is a large reasoning-focused model with 8.19 billion parameters, built on the qwen3 architecture. It has been downloaded 140,656 times.
Under the hood it uses 36 transformer layers, a hidden size of 4,096, 32 attention heads. It uses grouped-query attention (32 query heads sharing 8 key/value heads), which already trims KV-cache memory compared with full multi-head attention.
To run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF locally at a 4,096-token context, its quantized versions need between 4.42 GB (Q2_K, lowest quality) and 16.63 GB (GGUF, highest quality) of memory, weights plus KV cache and a system margin included. Context length drives that memory directly: at 4,096 tokens the KV cache for DeepSeek-R1-0528-Qwen3-8B-GGUF is about 0.56 GB, rising to roughly 18.0 GB at its full 131,072-token context. Shorter prompts free up memory for a higher-quality quantization.
For most users the best balance is Q6_K, needing about 7.63 GB. That means MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF fits entirely in the VRAM of a 6 GB GPU or larger, running fully on the GPU.
Available GGUF quantizations for MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF include Q2_K, Q3_K_M, Q3_K_L, Q4_K_M, Q5_K_M, Q6_K, GGUF. The model supports a native context length of up to 131,072 tokens; a longer context grows the KV cache and the memory needed.
GGUF file size and memory by quantization
Compare real GGUF weight sizes, estimated KV cache and total memory for Q4, Q5, Q8 and every quantization published in this repository.
| Quant. | Bits | Quality | Weights | KV | Total | Speed~ | Verdict |
|---|---|---|---|---|---|---|---|
| Q2_K | 3.21 | Low | 3.06 GB | 0.56 GB | 4.42 GB | 130.9 t/s | Fits in VRAM |
| Q3_K_M | 4.03 | Fair | 3.84 GB | 0.56 GB | 5.2 GB | 104.1 t/s | Fits in VRAM |
| Q3_K_L | 4.33 | Good | 4.13 GB | 0.56 GB | 5.49 GB | 96.9 t/s | Fits in VRAM |
| Q4_K_M | 4.91 | Good | 4.68 GB | 0.56 GB | 6.04 GB | 85.4 t/s | Fits in VRAM |
| Q5_K_M | 5.71 | Very good | 5.45 GB | 0.56 GB | 6.81 GB | 73.4 t/s | Fits in VRAM |
| Q6_K | 6.57 | Excellent | 6.26 GB | 0.56 GB | 7.63 GB | 63.9 t/s | Fits in VRAM |
| GGUF | 16.01 | Excellent | 15.26 GB | 0.56 GB | 16.63 GB | 3.3 t/s | Offload |
KV cache computed from the model's exact architecture. Speed is a rough estimate bounded by memory bandwidth.
Frequently asked questions
What kind of model is MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF?
MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF is a reasoning-focused model with 8.19 billion parameters, based on the qwen3 architecture. It is distributed as GGUF files for local inference.
How much VRAM do you need to run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF?
You need about 5.49 GB of VRAM to run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF entirely on the GPU using the Q3_K_L quantization (at a 4,096-token context). Smaller quantizations lower the requirement at the cost of quality.
Can I run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF on an 8 GB GPU?
Yes. With 8 GB of VRAM you can run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF fully on the GPU using Q6_K (about 7.63 GB).
Can I run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF on a 16 GB GPU?
Yes. With 16 GB of VRAM you can run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF fully on the GPU using Q6_K (about 7.63 GB).
Can I run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF on a 24 GB GPU?
Yes. With 24 GB of VRAM you can run MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF fully on the GPU using GGUF (about 16.63 GB).
What context length does MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF support?
MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF supports a native context length of up to 131,072 tokens. A longer context grows the KV cache, so it increases the memory needed to run the model.
What is the best quantization for MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF?
For MaziyarPanahi/DeepSeek-R1-0528-Qwen3-8B-GGUF, a strong default is Q4_K_M, which needs about 6.04 GB and keeps most of the quality while roughly halving the memory versus 8-bit. With VRAM to spare, Q5_K_M or Q6_K add a little more quality; if you are tight on memory, a smaller quantization still runs. Pick the highest quantization that fits your VRAM.