jwest33 · text

gemma-4-12B-it-null-space-abliterated

jwest33/gemma-4-12B-it-null-space-abliterated

gemma-4-12B-it-null-space-abliterated at Q4_K_M is exactly 7,381,382,688 bytes (6.87 GiB / 7.38 GB) — an effective 4.938 bits per weight, not the nominal 4. Its KV cache at 32K is 2.47 GiB, not the 12.00 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
12.0B
Architecture
gemma4
48 layers
Context
262,144
native (config.json)
License
gemma

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K4.50 GiB4,830,148,1283.231mradermacher
Q3_K_S5.15 GiB5,528,229,4083.698mradermacher
Q3_K_M5.67 GiB6,087,087,6484.072mradermacher
Q3_K_L6.12 GiB6,566,319,6484.392mradermacher
IQ4_XS6.23 GiB6,690,551,3284.475mradermacher
Q4_K_S6.54 GiB7,024,047,6484.699mradermacher
Q4_K_M6.87 GiB7,381,382,6884.938mradermacher
Q5_K_S7.77 GiB8,338,372,1285.578mradermacher
Q5_K_M7.96 GiB8,547,268,1285.717mradermacher
Q6_K9.11 GiB9,786,021,4086.546mradermacher
Q8_011.80 GiB12,669,646,3688.475mradermacher

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.72 GiB1.50 GiB2.09×8 / 40 / 0
8,1920.97 GiB3.00 GiB3.10×8 / 40 / 0
16,3841.47 GiB6.00 GiB4.09×8 / 40 / 0
32,7682.47 GiB12.00 GiB4.86×8 / 40 / 0
65,5364.47 GiB24.00 GiB5.37×8 / 40 / 0
131,0728.47 GiB48.00 GiB5.67×8 / 40 / 0

40 of 48 layers cache only a 1,024-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 6.27 GiB. The real file is 6.87 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 12.00 GiB at 32K context where the real figure is 2.47 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
48
Attention heads
16
KV heads
8
Head dim
256
Hidden size
3840
Vocab
262,144
Sliding window
1024
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does gemma-4-12B-it-null-space-abliterated need?
Q4_K_M is exactly 7,381,382,688 bytes (6.87 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-12B-it-null-space-abliterated's KV cache?
2.47 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-12B-it-null-space-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.