Cluj Napoca 0.2 needs about 17.3 GB of memory at Q4_K_M (a 15.3 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 11 quants, from 9.5 GB (Q2_K) to 27.1 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 5.9 GB.
Cluj Napoca 0.2 is a 25.5B-parameter Cluj model in GGUF format, quantized by mradermacher. Its trained context length is 195K tokens. The repository has 11 quant files, from 9.5 GB (Q2_K) to 27.1 GB (Q8_0).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 9.5 GB | 11.5 GB | Too big | Get file → | |
| Q3_K_S | 11.1 GB | 13.1 GB | Too big | Get file → | |
| Q3_K_M | 12.4 GB | 14.3 GB | Too big | Get file → | |
| Q3_K_L | 13.5 GB | 15.4 GB | Too big | Get file → | |
| IQ4_XS | 13.8 GB | 15.8 GB | Too big | Get file → | |
| Q4_K_S | 14.5 GB | 16.5 GB | Too big | Get file → | |
| Q4_K_M | 15.3 GB | 17.3 GB | Too big | Get file → | |
| Q5_K_S | 17.6 GB | 19.5 GB | Too big | Get file → | |
| Q5_K_M | 18.0 GB | 20.0 GB | Too big | Get file → | |
| Q6_K | 20.9 GB | 22.9 GB | Too big | Get file → | |
| Q8_0 | 27.1 GB | 29.0 GB | Too big | Get file → |
What GPU do you need for Cluj Napoca 0.2?
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 Q2_K (9.5 GB file, about 11.5 GB in use).
- 16 GB VRAM: the best quant that fits is IQ4_XS (13.8 GB file, about 15.8 GB in use).
- 24 GB VRAM: the best quant that fits is Q6_K (20.9 GB file, about 22.9 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (27.1 GB file, about 29.0 GB in use).
Which Cluj Napoca 0.2 quant should you choose?
Q4_K_M is the usual starting point for Cluj Napoca 0.2: it balances file size and quality well. Here it is a 15.3 GB file.
The Q8_0 file is 27.1 GB, about 1.8 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 9.5 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 Cluj Napoca 0.2
How much VRAM does Cluj Napoca 0.2 need?
About 17.3 GB at Q4_K_M with an 8K context window. That is the 15.3 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 Cluj Napoca 0.2 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 11.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Cluj Napoca 0.2 GGUF?
It depends on the quant: Q2_K is 9.5 GB, Q3_K_S is 11.1 GB, Q3_K_M is 12.4 GB, Q3_K_L is 13.5 GB, IQ4_XS is 13.8 GB, Q4_K_S is 14.5 GB and 5 more.
What context length does Cluj Napoca 0.2 support?
The GGUF header lists a trained context length of 200,000 tokens (195K). The KV cache grows with the context you use: about 1.5 GB at 8K and 5.9 GB at 32K.
Where can I download Cluj Napoca 0.2 GGUF?
The files are on Hugging Face in the mradermacher/Cluj-Napoca-0.2-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Cluj Napoca 0.2 use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.