Secure-deepseek-coder-v2-MoE needs about 13.1 GB of memory at Q4_K_M (a 10.4 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 14 quants, from 6.4 GB (Q2_K) to 16.7 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 9.1 GB.
15.7B parameter DeepSeek coder model with Mixture of Experts
Secure-deepseek-coder-v2-MoE is a 15.7B parameter model built on the DeepSeek architecture. It is optimized for coding tasks and supports a trained context of 163,840 tokens. The model is available in multiple GGUF quantizations.
Good at
- Coding assistance
- Code generation
- Bug detection
Limits
- No vision support
- License not specified
- Large VRAM requirement for higher quants
Best for
- Developers needing code generation
- Debugging code snippets
- Learning programming concepts
Who it’s for. Engineers and developers who require a large language model focused on coding. The model is suitable for integration into development tools and educational platforms.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 6.4 GB | 9.2 GB | Too big | Get file → | |
| IQ3_XS | 7.1 GB | 9.9 GB | Too big | Get file → | |
| IQ3_S | 7.5 GB | 10.3 GB | Too big | Get file → | |
| Q3_K_S | 7.5 GB | 10.3 GB | Too big | Get file → | |
| IQ3_M | 7.6 GB | 10.3 GB | Too big | Get file → | |
| Q3_K_M | 8.1 GB | 10.9 GB | Too big | Get file → | |
| Q3_K_L | 8.5 GB | 11.2 GB | Too big | Get file → | |
| IQ4_XS | 8.6 GB | 11.4 GB | Too big | Get file → | |
| Q4_K_S | 9.5 GB | 12.3 GB | Too big | Get file → | |
| Q4_K_M | 10.4 GB | 13.1 GB | Too big | Get file → | |
| Q5_K_S | 11.1 GB | 13.9 GB | Too big | Get file → | |
| Q5_K_M | 11.9 GB | 14.6 GB | Too big | Get file → | |
| Q6_K | 14.1 GB | 16.8 GB | Too big | Get file → | |
| Q8_0 | 16.7 GB | 19.5 GB | Too big | Get file → |
For 8 GB VRAM, the Q2_K quant (6.43 GB file, 9.2 GB memory at 8 k context) is the smallest available but still exceeds 8 GB. The Q4_K_M quant (10.36 GB file, 13.1 GB memory) offers better quality for systems with 13 GB or more VRAM. Choose the quant that fits your memory budget.
What GPU do you need for Secure-deepseek-coder-v2-MoE?
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: the best quant that fits is IQ4_XS (8.6 GB file, about 11.4 GB in use).
- 16 GB VRAM: the best quant that fits is Q5_K_M (11.9 GB file, about 14.6 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (16.7 GB file, about 19.5 GB in use).
Which Secure-deepseek-coder-v2-MoE quant should you choose?
Q4_K_M is the usual starting point for Secure-deepseek-coder-v2-MoE: it balances file size and quality well. Here it is a 10.4 GB file.
The Q8_0 file is 16.7 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q2_K at 6.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 Secure-deepseek-coder-v2-MoE
How much VRAM does Secure-deepseek-coder-v2-MoE need?
About 13.1 GB at Q4_K_M with an 8K context window. That is the 10.4 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 Secure-deepseek-coder-v2-MoE on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 9.2 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Secure-deepseek-coder-v2-MoE GGUF?
It depends on the quant: Q2_K is 6.4 GB, IQ3_XS is 7.1 GB, IQ3_S is 7.5 GB, Q3_K_S is 7.5 GB, IQ3_M is 7.6 GB, Q3_K_M is 8.1 GB and 8 more.
What context length does Secure-deepseek-coder-v2-MoE support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 2.3 GB at 8K and 9.1 GB at 32K.
Where can I download Secure-deepseek-coder-v2-MoE GGUF?
The files are on Hugging Face in the mradermacher/Secure-deepseek-coder-v2-MoE-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run this model on 8 GB VRAM?
The smallest quant requires 9.2 GB memory at 8 k context, so 8 GB VRAM is insufficient.
Does the model support image input?
No, the model has no vision capabilities.
What context length does the model support?
The model was trained on 163,840 tokens of context.