walledguard c needs about 1.0 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 11 quants, from 0.3 GB (Q3_K_S) to 1.0 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.4 GB.
walledguard c is a 494M-parameter Walledguard model in GGUF format, quantized by larenspear. Its trained context length is 32K tokens. The repository has 11 quant files, from 0.3 GB (Q3_K_S) to 1.0 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 0.3 GB | 0.9 GB | Fits | Get file → | |
| Q2_K | 0.3 GB | 0.9 GB | Fits | Get file → | |
| Q3_K_M | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q3_K_L | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q4_K_S | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q4_K_M | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q5_K_S | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q5_K_M | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q6_K | 0.5 GB | 1.1 GB | Fits | Get file → | |
| Q8_0 | 0.5 GB | 1.1 GB | Fits | Get file → | |
| F16 | 1.0 GB | 1.6 GB | Fits | Get file → |
What GPU do you need for walledguard c?
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: the best quant that fits is F16 (1.0 GB file, about 1.6 GB in use).
Which walledguard c quant should you choose?
Q4_K_M is the usual starting point for walledguard c: it balances file size and quality well. Here it is a 0.4 GB file.
The Q8_0 file is 0.5 GB, about 1.3 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 Q3_K_S at 0.3 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 walledguard c
How much VRAM does walledguard c need?
About 1.0 GB at Q4_K_M with an 8K context window. That is the 0.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 walledguard c on an 8 GB GPU?
Yes, with F16: the 1.0 GB file needs about 1.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of walledguard c GGUF?
It depends on the quant: Q3_K_S is 0.3 GB, Q2_K is 0.3 GB, Q3_K_M is 0.4 GB, Q3_K_L is 0.4 GB, Q4_K_S is 0.4 GB, Q4_K_M is 0.4 GB and 5 more.
What context length does walledguard c support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.1 GB at 8K and 0.4 GB at 32K.
Where can I download walledguard c GGUF?
The files are on Hugging Face in the larenspear/walledguard-c-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.