kai-os · text

Grug-12B

kai-os/Grug-12B

Grug-12B at Q4_K_M is exactly 7,381,384,128 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
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S2.78 GiB2,983,693,8881.996mradermacher
I1-IQ1_M2.98 GiB3,202,850,3682.142mradermacher
I1-IQ2_XXS3.32 GiB3,568,111,1682.387mradermacher
I1-IQ2_XS3.62 GiB3,887,844,9282.601mradermacher
I1-IQ2_S3.80 GiB4,079,599,1682.729mradermacher
I1-IQ2_M4.07 GiB4,371,807,8082.924mradermacher
I1-Q2_K_S4.19 GiB4,504,149,5683.013mradermacher
IQ2_S4.39 GiB4,708,744,3203.150bartowski
I1-Q2_K4.50 GiB4,830,150,2083.231mradermacher
I1-IQ3_XXS4.52 GiB4,849,196,6083.244mradermacher
IQ2_M4.60 GiB4,940,987,5203.305bartowski
Q2_K4.73 GiB5,077,875,8403.397bartowski
IQ3_XXS4.79 GiB5,145,091,2003.442bartowski
I1-IQ3_XS4.91 GiB5,272,395,3283.527mradermacher
Q2_K_L4.96 GiB5,321,669,7603.560bartowski
IQ3_XS5.15 GiB5,525,773,4403.696bartowski
I1-IQ3_S5.15 GiB5,528,231,4883.698mradermacher
I1-Q3_K_S5.15 GiB5,528,231,4883.698mradermacher
Q3_K_S5.33 GiB5,724,839,0403.829bartowski
I1-IQ3_M5.34 GiB5,733,994,0483.836mradermacher
IQ3_M5.56 GiB5,969,923,2003.993bartowski
I1-Q3_K_M5.67 GiB6,087,089,7284.072mradermacher
Q3_K_M5.87 GiB6,301,392,0004.215bartowski
I1-Q3_K_L6.12 GiB6,566,321,7284.392mradermacher
I1-IQ4_XS6.18 GiB6,635,257,4084.438mradermacher
Q3_K_L6.20 GiB6,652,828,8004.450bartowski
IQ4_XS6.32 GiB6,780,746,8804.536bartowski
I1-IQ4_NL6.50 GiB6,975,880,7684.666mradermacher
I1-Q4_06.52 GiB6,997,999,1684.681mradermacher
I1-Q4_K_S6.54 GiB7,024,049,7284.699mradermacher
IQ4_NL6.62 GiB7,105,641,6004.753bartowski
Q4_06.64 GiB7,127,760,0004.768bartowski
Q4_K_S6.68 GiB7,169,539,2004.796bartowski
Q4_K_M6.87 GiB7,381,384,1284.938kai-os
I1-Q4_K_M6.87 GiB7,381,384,7684.938mradermacher
I1-Q4_17.13 GiB7,657,127,4885.122mradermacher
Q4_K_M7.14 GiB7,662,533,7605.126bartowski
Q4_17.22 GiB7,755,431,0405.188bartowski
Q4_K_L7.36 GiB7,906,327,6805.289bartowski
I1-Q5_K_S7.77 GiB8,338,374,2085.578mradermacher

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 Grug-12B need?
Q4_K_M is exactly 7,381,384,128 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 Grug-12B'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 Grug-12B 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.