c4ai command r GGUF fixed pretokenizer needs about 32.8 GB of memory at Q4_K_M (a 21.5 GB file) with an 8K context window, so it fits on a 48 GB GPU. This repository has 5 quants, from 20.2 GB (Q4_0) to 28.7 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 42.9 GB.
c4ai command r GGUF fixed pretokenizer is a 35B-parameter Command R model in GGUF format, quantized by Jobaar. Its trained context length is 128K tokens. The repository has 5 quant files, from 20.2 GB (Q4_0) to 28.7 GB (Q6_K).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 20.2 GB | 31.5 GB | Too big | Get file → | |
| Q4_K_M | 21.5 GB | 32.8 GB | Too big | Get file → | |
| Q5_0 | 24.3 GB | 35.6 GB | Too big | Get file → | |
| Q5_K_M | 25.0 GB | 36.2 GB | Too big | Get file → | |
| Q6_K | 28.7 GB | 39.9 GB | Too big | Get file → |
What GPU do you need for c4ai command r GGUF fixed pretokenizer?
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: the best quant that fits is Q4_0 (20.2 GB file, about 31.5 GB in use).
- 48 GB VRAM: the best quant that fits is Q6_K (28.7 GB file, about 39.9 GB in use).
Which c4ai command r GGUF fixed pretokenizer quant should you choose?
Q4_K_M is the usual starting point for c4ai command r GGUF fixed pretokenizer: it balances file size and quality well. Here it is a 21.5 GB file.
If memory is tight, the smallest file is Q4_0 at 20.2 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about c4ai command r GGUF fixed pretokenizer
How much VRAM does c4ai command r GGUF fixed pretokenizer need?
About 32.8 GB at Q4_K_M with an 8K context window. That is the 21.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 c4ai command r GGUF fixed pretokenizer on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 31.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of c4ai command r GGUF fixed pretokenizer GGUF?
It depends on the quant: Q4_0 is 20.2 GB, Q4_K_M is 21.5 GB, Q5_0 is 24.3 GB, Q5_K_M is 25.0 GB, Q6_K is 28.7 GB.
What context length does c4ai command r GGUF fixed pretokenizer support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 10.7 GB at 8K and 42.9 GB at 32K.
Where can I download c4ai command r GGUF fixed pretokenizer GGUF?
The files are on Hugging Face in the Jobaar/c4ai-command-r-GGUF-fixed_pretokenizer repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does c4ai command r GGUF fixed pretokenizer use?
Hugging Face lists the license as unknown. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.