Huihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliterated
huihui-ai/Huihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliteratedHuihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliterated at Q4_K_M is exactly 3,416,119,296 bytes (3.18 GiB / 3.42 GB) — an effective 5.354 bits per weight, not the nominal 4. Its KV cache at 32K is 0.25 GiB, not the 1.09 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| I1-IQ1_S | 2.16 GiB | 2,315,865,408 | 3.630 | — | mradermacher |
| I1-IQ1_M | 2.19 GiB | 2,355,383,616 | 3.692 | — | mradermacher |
| I1-IQ2_XXS | 2.25 GiB | 2,421,247,296 | 3.795 | — | mradermacher |
| I1-IQ2_XS | 2.31 GiB | 2,478,067,008 | 3.884 | — | mradermacher |
| I1-IQ2_S | 2.33 GiB | 2,500,480,320 | 3.919 | — | mradermacher |
| I1-IQ2_M | 2.38 GiB | 2,553,171,264 | 4.002 | — | mradermacher |
| I1-IQ3_XXS | 2.47 GiB | 2,648,083,776 | 4.150 | — | mradermacher |
| I1-Q2_K_S | 2.72 GiB | 2,923,367,744 | 4.582 | — | mradermacher |
| Q2_K | 2.78 GiB | 2,980,654,080 | 4.672 | — | mradermacher |
| I1-Q2_K | 2.78 GiB | 2,980,654,400 | 4.672 | — | mradermacher |
| I1-IQ3_XS | 2.85 GiB | 3,060,219,200 | 4.796 | — | mradermacher |
| Q3_K_S | 2.89 GiB | 3,102,077,952 | 4.862 | — | mradermacher |
| I1-Q3_K_S | 2.89 GiB | 3,102,078,272 | 4.862 | — | mradermacher |
| I1-IQ3_S | 2.89 GiB | 3,103,018,304 | 4.863 | — | mradermacher |
| I1-IQ3_M | 2.91 GiB | 3,125,579,072 | 4.899 | — | mradermacher |
| Q3_K_M | 2.97 GiB | 3,191,958,528 | 5.003 | — | mradermacher |
| I1-Q3_K_M | 2.97 GiB | 3,191,958,848 | 5.003 | — | mradermacher |
| Q3_K_L | 3.05 GiB | 3,271,781,376 | 5.128 | — | mradermacher |
| I1-Q3_K_L | 3.05 GiB | 3,271,781,696 | 5.128 | — | mradermacher |
| I1-IQ4_XS | 3.07 GiB | 3,292,400,960 | 5.160 | — | mradermacher |
| IQ4_XS | 3.07 GiB | 3,298,298,880 | 5.169 | — | mradermacher |
| I1-IQ4_NL | 3.12 GiB | 3,350,400,320 | 5.251 | — | mradermacher |
| I1-Q4_0 | 3.12 GiB | 3,351,874,880 | 5.253 | — | mradermacher |
| Q4_K_S | 3.12 GiB | 3,354,430,464 | 5.257 | — | mradermacher |
| I1-Q4_K_S | 3.12 GiB | 3,354,430,784 | 5.257 | — | mradermacher |
| Q4_K_M | 3.18 GiB | 3,416,119,296 | 5.354 | — | mradermacher |
| I1-Q4_K_M | 3.18 GiB | 3,416,119,616 | 5.354 | — | mradermacher |
| I1-Q4_1 | 3.23 GiB | 3,465,956,672 | 5.432 | — | mradermacher |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.05 GiB | 0.14 GiB | 2.50× | 7 / 28 / 0 |
| 8,192 | 0.08 GiB | 0.27 GiB | 3.33× | 7 / 28 / 0 |
| 16,384 | 0.14 GiB | 0.55 GiB | 4.00× | 7 / 28 / 0 |
| 32,768 | 0.25 GiB | 1.09 GiB | 4.44× | 7 / 28 / 0 |
| 65,536 | 0.46 GiB | 2.19 GiB | 4.71× | 7 / 28 / 0 |
| 131,072 | 0.90 GiB | 4.38 GiB | 4.85× | 7 / 28 / 0 |
28 of 35 layers cache only a 512-token window rather than the full context, on a period of . Figures assume the default configuration; --swa-full disables the saving entirely.
Compare with
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 2.67 GiB. The real file is 3.18 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 1.09 GiB at 32K context where the real figure is 0.25 GiB, because most of this model's layers cache a fixed window rather than the whole context.
Architecture
Questions people ask
- How much VRAM does Huihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliterated need?
- Q4_K_M is exactly 3,416,119,296 bytes (3.18 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
- How large is Huihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliterated's KV cache?
- 0.25 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
- Which quantization of Huihui-gemma-4-E2B-it-qat-q4_0-unquantized-abliterated should I use?
- Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.