Tiny Purr 350M Merged needs about 1.3 GB of memory at Q4_K_M (a 0.2 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 25 quants, from 0.0 GB to 0.3 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 2.1 GB.
Tiny Purr 350M Merged is a 354M-parameter Tiny model in GGUF format, quantized by mradermacher. Its trained context length is 125K tokens. The repository has 25 quant files, from 0.0 GB to 0.3 GB (Q6_K).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 1.0 GB | Fits | Get file → | |
| IQ1_S | 0.1 GB | 1.1 GB | Fits | Get file → | |
| IQ1_M | 0.1 GB | 1.2 GB | Fits | Get file → | |
| IQ2_XXS | 0.1 GB | 1.2 GB | Fits | Get file → | |
| IQ2_XS | 0.1 GB | 1.2 GB | Fits | Get file → | |
| IQ2_S | 0.1 GB | 1.2 GB | Fits | Get file → | |
| IQ2_M | 0.1 GB | 1.2 GB | Fits | Get file → | |
| Q2_K_S | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ3_XXS | 0.2 GB | 1.2 GB | Fits | Get file → | |
| Q2_K | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ3_XS | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ3_S | 0.2 GB | 1.2 GB | Fits | Get file → | |
| Q3_K_S | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ3_M | 0.2 GB | 1.2 GB | Fits | Get file → | |
| Q3_K_M | 0.2 GB | 1.2 GB | Fits | Get file → | |
| Q3_K_L | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ4_XS | 0.2 GB | 1.2 GB | Fits | Get file → | |
| IQ4_NL | 0.2 GB | 1.3 GB | Fits | Get file → | |
| Q4_0 | 0.2 GB | 1.3 GB | Fits | Get file → | |
| Q4_K_S | 0.2 GB | 1.3 GB | Fits | Get file → | |
| Q4_K_M | 0.2 GB | 1.3 GB | Fits | Get file → | |
| Q4_1 | 0.2 GB | 1.3 GB | Fits | Get file → | |
| Q5_K_S | 0.3 GB | 1.3 GB | Fits | Get file → | |
| Q5_K_M | 0.3 GB | 1.3 GB | Fits | Get file → | |
| Q6_K | 0.3 GB | 1.3 GB | Fits | Get file → |
What GPU do you need for Tiny Purr 350M Merged?
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 Q6_K (0.3 GB file, about 1.3 GB in use).
Which Tiny Purr 350M Merged quant should you choose?
Q4_K_M is the usual starting point for Tiny Purr 350M Merged: it balances file size and quality well. Here it is a 0.2 GB file.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Tiny Purr 350M Merged
How much VRAM does Tiny Purr 350M Merged need?
About 1.3 GB at Q4_K_M with an 8K context window. That is the 0.2 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 Tiny Purr 350M Merged on an 8 GB GPU?
Yes, with Q6_K: the 0.3 GB file needs about 1.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Tiny Purr 350M Merged GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 0.1 GB, IQ1_M is 0.1 GB, IQ2_XXS is 0.1 GB, IQ2_XS is 0.1 GB, IQ2_S is 0.1 GB and 19 more.
What context length does Tiny Purr 350M Merged support?
The GGUF header lists a trained context length of 128,000 tokens (125K). The KV cache grows with the context you use: about 0.5 GB at 8K and 2.1 GB at 32K.
Where can I download Tiny Purr 350M Merged GGUF?
The files are on Hugging Face in the mradermacher/Tiny-Purr-350M-merged-i1-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 Tiny Purr 350M Merged use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.