Vikhrmodels · text

Vikhr-Gemma-2B-instruct

Vikhrmodels/Vikhr-Gemma-2B-instruct

Vikhr-Gemma-2B-instruct at Q4_K_M is exactly 1,708,582,848 bytes (1.59 GiB / 1.71 GB) — an effective 5.228 bits per weight, not the nominal 4. Its KV cache at 32K is 1.85 GiB, not the 3.25 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
2.6B
Architecture
gemma2
26 layers
Context
8,192
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ1_S0.78 GiB832,160,0962.546Vikhrmodels
IQ1_M0.81 GiB873,797,9842.674Vikhrmodels
IQ2_XXS0.88 GiB943,194,4642.886Vikhrmodels
IQ2_XS0.93 GiB1,002,545,5043.068Vikhrmodels
IQ2_S0.96 GiB1,032,497,5043.159Vikhrmodels
IQ2_M1.01 GiB1,088,014,6883.329Vikhrmodels
Q2_K_S1.09 GiB1,170,000,2243.580Vikhrmodels
IQ3_XXS1.10 GiB1,181,686,1123.616Vikhrmodels
Q2_K1.15 GiB1,229,830,4963.763Vikhrmodels
IQ3_XS1.22 GiB1,314,212,1924.021Vikhrmodels
IQ3_S1.27 GiB1,360,660,8324.164Vikhrmodels
Q3_K_S1.27 GiB1,360,660,8324.164Vikhrmodels
IQ3_M1.30 GiB1,393,561,8244.264bartowski
IQ3_M1.30 GiB1,393,561,9524.264Vikhrmodels
Q3_K1.36 GiB1,461,668,1924.473Vikhrmodels
Q3_K_M1.36 GiB1,461,668,1924.473Vikhrmodels
Q3_K_L1.44 GiB1,550,436,5764.744bartowski
Q3_K_L1.44 GiB1,550,436,7044.744Vikhrmodels
IQ4_XS1.46 GiB1,566,251,2324.793bartowski
IQ4_XS1.46 GiB1,566,251,3604.793Vikhrmodels
Q4_01.52 GiB1,629,509,5684.986Vikhrmodels
IQ4_NL1.52 GiB1,629,509,9844.986Vikhrmodels
Q4_K_S1.53 GiB1,638,651,8405.014Vikhrmodels
Q4_K_S1.53 GiB1,638,652,1285.014bartowski
Q4_K_M1.59 GiB1,708,582,8485.228Vikhrmodels
Q4_K1.59 GiB1,708,582,8485.228Vikhrmodels
Q4_K_M1.59 GiB1,708,583,1365.228bartowski
Q4_11.64 GiB1,756,026,8165.373Vikhrmodels
Q4_K_L1.72 GiB1,851,431,1365.665bartowski
Q5_01.75 GiB1,882,544,0645.761Vikhrmodels
Q5_K_S1.75 GiB1,882,544,0645.761Vikhrmodels
Q5_K_S1.75 GiB1,882,544,3525.761bartowski
Q5_K_M1.79 GiB1,923,278,7845.885Vikhrmodels
Q5_K1.79 GiB1,923,278,7845.885Vikhrmodels
Q5_K_M1.79 GiB1,923,279,0725.885bartowski
Q5_11.87 GiB2,009,061,3126.148Vikhrmodels
Q5_K_L1.92 GiB2,066,127,0726.322bartowski
Q6_K2.00 GiB2,151,393,2166.583Vikhrmodels
Q6_K2.00 GiB2,151,393,5046.583bartowski
Q6_K_L2.14 GiB2,294,241,5047.021bartowski

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.41 GiB0.41 GiB13 / 13 / 0
8,1920.63 GiB0.81 GiB1.28×13 / 13 / 0
16,3841.04 GiB1.63 GiB1.56×13 / 13 / 0
32,7681.85 GiB3.25 GiB1.75×13 / 13 / 0
65,5363.48 GiB6.50 GiB1.87×13 / 13 / 0
131,0726.73 GiB13.00 GiB1.93×13 / 13 / 0

13 of 26 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 1.37 GiB. The real file is 1.59 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 3.25 GiB at 32K context where the real figure is 1.85 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
26
Attention heads
8
KV heads
4
Head dim
256
Hidden size
2304
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 Vikhr-Gemma-2B-instruct need?
Q4_K_M is exactly 1,708,582,848 bytes (1.59 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Vikhr-Gemma-2B-instruct's KV cache?
1.85 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 Vikhr-Gemma-2B-instruct 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.