DeepSeek-Coder-V2-Instruct needs about 183.2 GB of memory at Q4_K_M (a 142.5 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 4 quants, from 101.7 GB (Q3_K_S) to 142.5 GB (Q4_K_M). 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 LoneStriker. Its trained context length is 160K tokens. The repository has 4 quant files, from 101.7 GB (Q3_K_S) to 142.5 GB (Q4_K_M).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 101.7 GB (4 parts) | 142.4 GB | Too big | Get file → | |
| Q3_K_M | 112.7 GB (4 parts) | 153.4 GB | Too big | Get file → | |
| Q3_K_L | 122.4 GB (4 parts) | 163.1 GB | Too big | Get file → | |
| Q4_K_M | 142.5 GB (4 parts) | 183.2 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?
Q4_K_M is the usual starting point for DeepSeek-Coder-V2-Instruct: it balances file size and quality well. Here it is a 142.5 GB file.
If memory is tight, the smallest file is Q3_K_S at 101.7 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about DeepSeek-Coder-V2-Instruct
How much VRAM does DeepSeek-Coder-V2-Instruct need?
About 183.2 GB at Q4_K_M with an 8K context window. That is the 142.5 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 142.4 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: Q3_K_S is 101.7 GB, Q3_K_M is 112.7 GB, Q3_K_L is 122.4 GB, Q4_K_M is 142.5 GB.
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 LoneStriker/DeepSeek-Coder-V2-Instruct-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.