gpt2bis needs about 0.9 GB of memory at Q4_K_M (a 0.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 24 quants, from 0.1 GB (Q2_K) to 0.3 GB (F16).
gpt2bis is a 163M-parameter Gpt model in GGUF format, quantized by batmac. Its trained context length is 1K tokens. The repository has 24 quant files, from 0.1 GB (Q2_K) to 0.3 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ3_XXS | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ3_XS | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ3_S | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q3_K_S | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ3_M | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q3_K | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q3_K_M | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q3_K_L | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ4_XS | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q4_0 | 0.1 GB | 0.6 GB | Fits | Get file → | |
| IQ4_NL | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q4_K_S | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q4_K | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q4_K_M | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q4_1 | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q5_0 | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q5_K_S | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q5_K | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q5_K_M | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q5_1 | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q6_K | 0.1 GB | 0.7 GB | Fits | Get file → | |
| Q8_0 | 0.2 GB | 0.7 GB | Fits | Get file → | |
| F16 | 0.3 GB | 0.9 GB | Fits | Get file → |
What GPU do you need for gpt2bis?
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 (0.3 GB file, about 1.1 GB in use).
Which gpt2bis quant should you choose?
Q4_K_M is the usual starting point for gpt2bis: it balances file size and quality well. Here it is a 0.1 GB file.
The Q8_0 file is 0.2 GB, about 1.6 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 0.1 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
Frequently asked questions about gpt2bis
How much VRAM does gpt2bis need?
About 0.9 GB at Q4_K_M with an 8K context window. That is the 0.1 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 gpt2bis on an 8 GB GPU?
Yes, with F16: the 0.3 GB file needs about 1.1 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of gpt2bis GGUF?
It depends on the quant: Q2_K is 0.1 GB, IQ3_XXS is 0.1 GB, IQ3_XS is 0.1 GB, IQ3_S is 0.1 GB, Q3_K_S is 0.1 GB, IQ3_M is 0.1 GB and 18 more.
What context length does gpt2bis support?
The GGUF header lists a trained context length of 1,024 tokens (1K). The KV cache grows with the context you use: about 0.3 GB at 8K and 0.0 GB at 1K.
Where can I download gpt2bis GGUF?
The files are on Hugging Face in the batmac/gpt2-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.