google · text

gemma-2-9b-it

google/gemma-2-9b-it

gemma-2-9b-it at Q4_K_M is exactly 5,761,057,472 bytes (5.37 GiB / 5.76 GB) — an effective 4.987 bits per weight, not the nominal 4. Its KV cache at 32K is 5.99 GiB, not the 10.50 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV from mirror (mirror:unsloth/gemma-2-9b-it)
Parameters
9.2B
Architecture
gemma2
42 layers
Context
8,192
native (config.json)
License
gemma

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ2_XS2.86 GiB3,067,381,6322.655bartowski
IQ2_S2.99 GiB3,211,487,1042.780bartowski
IQ2_M3.20 GiB3,434,668,9922.973bartowski
IQ3_XXS3.54 GiB3,796,739,0083.287bartowski
Q2_K3.54 GiB3,805,397,6963.294SanctumAI
Q2_K3.54 GiB3,805,397,9523.294bartowski
Q2_K_L3.75 GiB4,027,605,9523.486bartowski
IQ3_XS3.86 GiB4,144,989,1203.588bartowski
Q3_K_S4.04 GiB4,337,664,7043.755SanctumAI
Q3_K_S4.04 GiB4,337,664,9603.755bartowski
IQ3_M4.19 GiB4,494,615,4883.891bartowski
Q3_K_M4.43 GiB4,761,780,9284.122SanctumAI
Q3_K_M4.43 GiB4,761,781,1844.122464bartowski
Q3_K_L4.78 GiB5,132,452,5444.443SanctumAI
Q3_K_L4.78 GiB5,132,452,8004.443lmstudio-community
Q3_K_L4.78 GiB5,132,452,8004.443bartowski
IQ4_XS4.83 GiB5,183,030,2084.487lmstudio-community
IQ4_XS4.83 GiB5,183,030,2084.487bartowski
Q4_05.07 GiB5,443,142,3364.712464SanctumAI
Q4_K_S5.10 GiB5,478,924,9924.743SanctumAI
Q4_K_S5.10 GiB5,478,925,2484.743bartowski
Q4_K5.37 GiB5,761,057,4724.987SanctumAI
Q4_K_M5.37 GiB5,761,057,4724.987SanctumAI
Q4_K_M5.37 GiB5,761,057,7284.987bartowski
Q4_K_M5.37 GiB5,761,057,7284.987464lmstudio-community
Q4_15.55 GiB5,963,367,1045.162SanctumAI
Q4_K_L5.57 GiB5,983,265,7285.179bartowski
Q5_K_S6.04 GiB6,483,591,8725.612SanctumAI
Q5_06.04 GiB6,483,591,8725.612SanctumAI
Q5_K_S6.04 GiB6,483,592,1285.612bartowski
Q5_K6.19 GiB6,647,366,3365.754SanctumAI
Q5_K_M6.19 GiB6,647,366,3365.754SanctumAI
Q5_K_M6.19 GiB6,647,366,5925.754464lmstudio-community
Q5_K_M6.19 GiB6,647,366,5925.754bartowski
Q5_K_L6.40 GiB6,869,574,5925.947bartowski
Q5_16.52 GiB7,003,816,6406.063SanctumAI
Q6_K7.07 GiB7,589,069,5046.569SanctumAI
Q6_K7.07 GiB7,589,069,7606.569464lmstudio-community
Q6_K7.07 GiB7,589,069,7606.569bartowski
Q6_K_L7.27 GiB7,811,277,7606.762bartowski

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0961.31 GiB1.31 GiB21 / 21 / 0
8,1922.05 GiB2.63 GiB1.28×21 / 21 / 0
16,3843.36 GiB5.25 GiB1.56×21 / 21 / 0
32,7685.99 GiB10.50 GiB1.75×21 / 21 / 0
65,53611.24 GiB21.00 GiB1.87×21 / 21 / 0
131,07221.74 GiB42.00 GiB1.93×21 / 21 / 0

21 of 42 layers cache only a 4,096-token window rather than the full context, on a period of 2. 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 4.84 GiB. The real file is 5.37 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 10.50 GiB at 32K context where the real figure is 5.99 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from mirror:unsloth/gemma-2-9b-it
Layers
42
Attention heads
16
KV heads
8
Head dim
256
Hidden size
3584
Vocab
256,000
Sliding window
4096
SWA period
2
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does gemma-2-9b-it need?
Q4_K_M is exactly 5,761,057,472 bytes (5.37 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-2-9b-it's KV cache?
5.99 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-2-9b-it 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.