josephmayo/Holo-3.1-9B-Coder needs about 7.2 GB of memory at Q4_K_M (a 5.6 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 3 quants, from 5.6 GB (Q4_K_M) to 7.4 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.
Holo-3.1-9B-Coder – code‑specialized Qwen3.5 model
Holo-3.1-9B-Coder is a 8.95B parameter model adapted for coding tasks. It builds on Hcompany/Holo-3.1-9B and uses Qwen3.5 architecture. The model is released under Apache‑2.0 and is available in three GGUF quantizations.
Good at
- Coding assistance
- Adapter‑based code generation
- Local deployment
Limits
- No vision support
- Generated code requires review
- Limited to 262144 context tokens
Best for
- Local code generation
- Fine‑tuning for coding
- Embedding in agent workflows
Who it’s for. Developers needing a local, code‑focused LLM. The model is suitable for projects that require on‑premise inference and can handle the 262144 token context. It is ideal for teams that prefer open‑source licensing and want to integrate coding capabilities into agents.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 5.6 GB | 7.2 GB | Tight | Get file → | |
| Q5_K_M | 6.5 GB | 8.0 GB | Too big | Get file → | |
| Q6_K | 7.4 GB | 8.9 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_M (file size 5.63 GB, estimated 7.2 GB memory). For 10 GB VRAM, Q5_K_M (6.47 GB, 8 GB memory) is suitable. If you have 12 GB or more, Q6_K (7.36 GB, 8.9 GB memory) can be used. Memory estimates are approximate.
What GPU do you need for josephmayo/Holo-3.1-9B-Coder?
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: the best quant that fits is Q5_K_M (6.5 GB file, about 8.0 GB in use).
- 12 GB VRAM: the best quant that fits is Q6_K (7.4 GB file, about 8.9 GB in use).
Which josephmayo/Holo-3.1-9B-Coder quant should you choose?
Q4_K_M is the usual starting point for josephmayo/Holo-3.1-9B-Coder: it balances file size and quality well. Here it is a 5.6 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about josephmayo/Holo-3.1-9B-Coder
How much VRAM does josephmayo/Holo-3.1-9B-Coder need?
About 7.2 GB at Q4_K_M with an 8K context window. That is the 5.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 josephmayo/Holo-3.1-9B-Coder on an 8 GB GPU?
Yes, with Q5_K_M: the 6.5 GB file needs about 8.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of josephmayo/Holo-3.1-9B-Coder GGUF?
It depends on the quant: Q4_K_M is 5.6 GB, Q5_K_M is 6.5 GB, Q6_K is 7.4 GB.
What context length does josephmayo/Holo-3.1-9B-Coder support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.3 GB at 32K.
Where can I download josephmayo/Holo-3.1-9B-Coder GGUF?
The files are on Hugging Face in the josephmayo/Holo-3.1-9B-Coder repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does josephmayo/Holo-3.1-9B-Coder use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run Holo-3.1-9B-Coder on 8 GB VRAM?
Yes, the Q4_K_M quantization requires about 7.2 GB of VRAM at 8k context, which fits within 8 GB.
Does the model support vision tasks?
No, Holo-3.1-9B-Coder does not include vision capabilities.
Is the code output safe to run directly?
Generated code should be reviewed before execution; the model does not guarantee safety.