ToastyPigeon gemma 3 starshine merge A needs about 11.0 GB of memory at Q4_K_M (a 7.3 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 6 quants, from 6.9 GB (Q4_K_S) to 12.5 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 12.9 GB.
ToastyPigeon gemma 3 starshine merge A is a 11.8B-parameter Gemma model in GGUF format, quantized by ArtusDev. Its trained context length is 128K tokens. The repository has 6 quant files, from 6.9 GB (Q4_K_S) to 12.5 GB (Q8_0).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_S | 6.9 GB | 10.7 GB | Too big | Get file → | |
| Q4_K_M | 7.3 GB | 11.0 GB | Too big | Get file → | |
| Q5_K_S | 8.2 GB | 12.0 GB | Too big | Get file → | |
| Q5_K_M | 8.4 GB | 12.2 GB | Too big | Get file → | |
| Q6_K | 9.7 GB | 13.4 GB | Too big | Get file → | |
| Q8_0 | 12.5 GB | 16.2 GB | Too big | Get file → |
What GPU do you need for ToastyPigeon gemma 3 starshine merge A?
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 Q5_K_S (8.2 GB file, about 12.0 GB in use).
- 16 GB VRAM: the best quant that fits is Q6_K (9.7 GB file, about 13.4 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (12.5 GB file, about 16.2 GB in use).
Which ToastyPigeon gemma 3 starshine merge A quant should you choose?
Q4_K_M is the usual starting point for ToastyPigeon gemma 3 starshine merge A: it balances file size and quality well. Here it is a 7.3 GB file.
The Q8_0 file is 12.5 GB, about 1.7 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 Q4_K_S at 6.9 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 ToastyPigeon gemma 3 starshine merge A
How much VRAM does ToastyPigeon gemma 3 starshine merge A need?
About 11.0 GB at Q4_K_M with an 8K context window. That is the 7.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 ToastyPigeon gemma 3 starshine merge A on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 10.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of ToastyPigeon gemma 3 starshine merge A GGUF?
It depends on the quant: Q4_K_S is 6.9 GB, Q4_K_M is 7.3 GB, Q5_K_S is 8.2 GB, Q5_K_M is 8.4 GB, Q6_K is 9.7 GB, Q8_0 is 12.5 GB.
What context length does ToastyPigeon gemma 3 starshine merge A support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 3.2 GB at 8K and 12.9 GB at 32K.
Where can I download ToastyPigeon gemma 3 starshine merge A GGUF?
The files are on Hugging Face in the ArtusDev/ToastyPigeon_gemma-3-starshine-merge-A-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.