AutoCoder needs about 22.5 GB of memory at Q4_K_M (a 19.9 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 2 quants, from 14.4 GB (Q3_K_S) to 19.9 GB (Q4_K_M).
AutoCoder – a 33.3B llama-based coding model
AutoCoder is a 33.3B parameter llama model focused on coding tasks. It supports a context length of 16384 tokens and is available in GGUF format. The model is provided by redponike and released under an unspecified license.
Good at
- Code generation
- Debugging assistance
- Language syntax understanding
Limits
- No vision support
- Large memory requirement
- No license details
Best for
- Developers needing code suggestions
- Automated code review tools
- Educational coding assistants
Who it’s for. Developers and researchers who need a large language model specialized in coding. The model is suitable for environments where code generation and debugging are primary tasks.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 14.4 GB | 17.0 GB | Too big | Get file → | |
| Q4_K_M | 19.9 GB | 22.5 GB | Too big | Get file → |
For systems with limited VRAM, the Q3_K_S quant (~14.42 GB file, ~17 GB memory at 8k context) is the smallest option. If you have more memory, Q4_K_M (~19.94 GB file, ~22.5 GB memory at 8k context) offers higher precision. Memory estimates are approximate.
What GPU do you need for AutoCoder?
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: the best quant that fits is Q4_K_M (19.9 GB file, about 22.5 GB in use).
Which AutoCoder quant should you choose?
Q4_K_M is the usual starting point for AutoCoder: it balances file size and quality well. Here it is a 19.9 GB file.
If memory is tight, the smallest file is Q3_K_S at 14.4 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
Source
Frequently asked questions about AutoCoder
How much VRAM does AutoCoder need?
About 22.5 GB at Q4_K_M with an 8K context window. That is the 19.9 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 AutoCoder on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 17.0 GB, so you would need a larger GPU or CPU offloading.
What is the file size of AutoCoder GGUF?
It depends on the quant: Q3_K_S is 14.4 GB, Q4_K_M is 19.9 GB.
What context length does AutoCoder support?
The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 2.1 GB at 8K and 4.2 GB at 16K.
Where can I download AutoCoder GGUF?
The files are on Hugging Face in the redponike/AutoCoder-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 AutoCoder on 8 GB VRAM?
No, the smallest quant requires about 17 GB of VRAM at 8k context.
Does AutoCoder support vision?
No, the model does not include vision capabilities.