HwiyeolJo testtt needs about 15.1 GB of memory at Q4_K_M (a 7.9 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 22 quants, from 4.1 GB (Q8_0) to 10.7 GB (Q6_K).
HwiyeolJo testtt is a 13B-parameter Hwiyeoljo model in GGUF format, quantized by RichardErkhov. Its trained context length is 4K tokens. The repository has 22 quant files, from 4.1 GB (Q8_0) to 10.7 GB (Q6_K).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 4.1 GB | 7.9 GB | Tight | Get file → | |
| Q2_K | 4.9 GB | 8.7 GB | Too big | Get file → | |
| IQ3_XS | 5.4 GB | 9.2 GB | Too big | Get file → | |
| IQ3_S | 5.7 GB | 9.5 GB | Too big | Get file → | |
| Q3_K_S | 5.7 GB | 9.5 GB | Too big | Get file → | |
| IQ3_M | 6.0 GB | 9.8 GB | Too big | Get file → | |
| Q5_K_M | 6.1 GB | 10.0 GB | Too big | Get file → | |
| Q5_K | 6.3 GB | 10.1 GB | Too big | Get file → | |
| Q3_K | 6.3 GB | 10.2 GB | Too big | Get file → | |
| Q3_K_M | 6.3 GB | 10.2 GB | Too big | Get file → | |
| Q3_K_L | 6.9 GB | 10.8 GB | Too big | Get file → | |
| IQ4_XS | 7.0 GB | 10.9 GB | Too big | Get file → | |
| Q4_0 | 7.4 GB | 11.2 GB | Too big | Get file → | |
| IQ4_NL | 7.4 GB | 11.3 GB | Too big | Get file → | |
| Q4_K_S | 7.4 GB | 11.3 GB | Too big | Get file → | |
| Q4_K | 7.9 GB | 11.7 GB | Too big | Get file → | |
| Q4_K_M | 7.9 GB | 11.7 GB | Too big | Get file → | |
| Q4_1 | 8.2 GB | 12.0 GB | Too big | Get file → | |
| Q5_0 | 9.0 GB | 12.8 GB | Too big | Get file → | |
| Q5_K_S | 9.0 GB | 12.8 GB | Too big | Get file → | |
| Q5_1 | 9.8 GB | 13.6 GB | Too big | Get file → | |
| Q6_K | 10.7 GB | 14.5 GB | Too big | Get file → |
What GPU do you need for HwiyeolJo testtt?
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 Q8_0 (4.1 GB file, about 11.3 GB in use).
- 16 GB VRAM: the best quant that fits is Q4_1 (8.2 GB file, about 15.4 GB in use).
- 24 GB VRAM: the best quant that fits is Q6_K (10.7 GB file, about 17.9 GB in use).
Which HwiyeolJo testtt quant should you choose?
Q4_K_M is the usual starting point for HwiyeolJo testtt: it balances file size and quality well. Here it is a 7.9 GB file.
The Q8_0 file is 4.1 GB, about 0.5 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 Q8_0 at 4.1 GB, with the quality trade-offs that come with fewer bits. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about HwiyeolJo testtt
How much VRAM does HwiyeolJo testtt need?
About 15.1 GB at Q4_K_M with an 8K context window. That is the 7.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 HwiyeolJo testtt on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 11.3 GB, so you would need a larger GPU or CPU offloading.
What is the file size of HwiyeolJo testtt GGUF?
It depends on the quant: Q8_0 is 4.1 GB, Q2_K is 4.9 GB, IQ3_XS is 5.4 GB, IQ3_S is 5.7 GB, Q3_K_S is 5.7 GB, IQ3_M is 6.0 GB and 16 more.
What context length does HwiyeolJo testtt support?
The GGUF header lists a trained context length of 4,096 tokens (4K). The KV cache grows with the context you use: about 6.7 GB at 8K and 3.4 GB at 4K.
Where can I download HwiyeolJo testtt GGUF?
The files are on Hugging Face in the RichardErkhov/HwiyeolJo_-_testtt-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.