WWTCyberLab · text

gemma-4-E2B-it-abliterated

WWTCyberLab/gemma-4-E2B-it-abliterated

gemma-4-E2B-it-abliterated at Q4_K_M is exactly 3,427,874,208 bytes (3.19 GiB / 3.43 GB) — an effective 5.353 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.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
5.1B
Architecture
gemma4
35 layers
Context
131,072
native (config.json)
License
gemma

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S2.16 GiB2,315,866,4003.616mradermacher
I1-IQ1_M2.19 GiB2,355,384,6083.678mradermacher
I1-IQ2_XXS2.25 GiB2,421,248,2883.781mradermacher
I1-IQ2_XS2.31 GiB2,478,068,0003.870mradermacher
I1-IQ2_S2.33 GiB2,500,481,3123.905mradermacher
I1-IQ2_M2.38 GiB2,553,172,2563.987mradermacher
I1-IQ3_XXS2.47 GiB2,648,084,7684.135mradermacher
I1-Q2_K_S2.72 GiB2,923,368,7364.565mradermacher
Q2_K2.78 GiB2,989,082,0164.668mradermacher
I1-Q2_K2.78 GiB2,989,082,3044.668mradermacher
I1-IQ3_XS2.85 GiB3,060,220,1924.779mradermacher
Q3_K_S2.90 GiB3,110,210,9764.857mradermacher
I1-Q3_K_S2.90 GiB3,110,211,2644.857mradermacher
I1-IQ3_S2.90 GiB3,112,404,6724.860mradermacher
I1-IQ3_M2.92 GiB3,134,965,4404.895mradermacher
Q3_K_M2.98 GiB3,201,344,9284.999mradermacher
I1-Q3_K_M2.98 GiB3,201,345,2164.999mradermacher
Q3_K_L3.06 GiB3,282,347,4245.125mradermacher
I1-Q3_K_L3.06 GiB3,282,347,7125.125mradermacher
I1-IQ4_XS3.08 GiB3,303,925,4405.159mradermacher
IQ4_XS3.08 GiB3,309,823,3925.168mradermacher
I1-IQ4_NL3.13 GiB3,362,219,7125.250mradermacher
I1-Q4_03.13 GiB3,362,514,6245.251mradermacher
Q4_K_S3.13 GiB3,365,070,2405.255mradermacher
I1-Q4_K_S3.13 GiB3,365,070,5285.255mradermacher
Q4_K_M3.19 GiB3,427,874,2085.353mradermacher
I1-Q4_K_M3.19 GiB3,427,874,4965.353mradermacher
I1-Q4_13.24 GiB3,477,776,0645.431mradermacher
Q5_K_S3.35 GiB3,595,396,5125.614mradermacher
I1-Q5_K_S3.35 GiB3,595,396,8005.614mradermacher
Q5_K_M3.38 GiB3,630,282,1445.669mradermacher
I1-Q5_K_M3.38 GiB3,630,282,4325.669mradermacher
Q6_K3.58 GiB3,845,340,5766.005mradermacher
I1-Q6_K3.58 GiB3,845,340,8646.005mradermacher
Q8_04.63 GiB4,967,490,9767.757mradermacher
F168.67 GiB9,311,298,97614.540mradermacher

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.05 GiB0.14 GiB2.50×7 / 28 / 0
8,1920.08 GiB0.27 GiB3.33×7 / 28 / 0
16,3840.14 GiB0.55 GiB4.00×7 / 28 / 0
32,7680.25 GiB1.09 GiB4.44×7 / 28 / 0
65,5360.46 GiB2.19 GiB4.71×7 / 28 / 0
131,0720.90 GiB4.38 GiB4.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

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 2.68 GiB. The real file is 3.19 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

from config.json
Layers
35
Attention heads
8
KV heads
1
Head dim
256
Hidden size
1536
Vocab
262,144
Sliding window
512
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does gemma-4-E2B-it-abliterated need?
Q4_K_M is exactly 3,427,874,208 bytes (3.19 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is gemma-4-E2B-it-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 gemma-4-E2B-it-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.