DeepSeek-Coder-V2-Instruct needs about 166.3 GB of memory at IQ4_XS (a 125.6 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 8 quants, from 47.4 GB (IQ1_S) to 250.6 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 161.1 GB.
DeepSeek-Coder-V2-Instruct is a 236B-parameter DeepSeek model in GGUF format, quantized by qwp4w3hyb. Its trained context length is 160K tokens. The repository has 8 quant files, from 47.4 GB (IQ1_S) to 250.6 GB (Q8_0).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 47.4 GB | 88.2 GB | Too big | Get file → | |
| IQ2_XXS | 61.5 GB (2 parts) | 102.3 GB | Too big | Get file → | |
| IQ3_XXS | 90.8 GB (2 parts) | 131.6 GB | Too big | Get file → | |
| IQ4_XS | 125.6 GB (3 parts) | 166.3 GB | Too big | Get file → | |
| Q4_0 | 133.4 GB (3 parts) | 174.2 GB | Too big | Get file → | |
| Q5_K_S | 162.3 GB (4 parts) | 203.1 GB | Too big | Get file → | |
| Q6_K | 193.5 GB (5 parts) | 234.3 GB | Too big | Get file → | |
| Q8_0 | 250.6 GB (6 parts) | 291.4 GB | Too big | Get file → |
What GPU do you need for DeepSeek-Coder-V2-Instruct?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: no quant fits at an 8K context.
- 32 GB VRAM: no quant fits at an 8K context.
- 48 GB VRAM: no quant fits at an 8K context.
Which DeepSeek-Coder-V2-Instruct quant should you choose?
IQ4_XS (125.6 GB) is the middle option in this repository. The usual sweet spot between file size and quality, and the quant most people start with.
If memory is tight, the smallest file is IQ1_S at 47.4 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DeepSeek-Coder-V2-Instruct
How much VRAM does DeepSeek-Coder-V2-Instruct need?
About 166.3 GB at IQ4_XS with an 8K context window. That is the 125.6 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run DeepSeek-Coder-V2-Instruct on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 88.2 GB, so you would need a larger GPU or CPU offloading.
What is the file size of DeepSeek-Coder-V2-Instruct GGUF?
It depends on the quant: IQ1_S is 47.4 GB, IQ2_XXS is 61.5 GB, IQ3_XXS is 90.8 GB, IQ4_XS is 125.6 GB, Q4_0 is 133.4 GB, Q5_K_S is 162.3 GB and 2 more.
What context length does DeepSeek-Coder-V2-Instruct support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 40.3 GB at 8K and 161.1 GB at 32K.
Where can I download DeepSeek-Coder-V2-Instruct GGUF?
The files are on Hugging Face in the qwp4w3hyb/DeepSeek-Coder-V2-Instruct-iMat-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does DeepSeek-Coder-V2-Instruct use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.