google · vision language · mixture of experts

diffusiongemma-26B-A4B-it

google/diffusiongemma-26B-A4B-it

diffusiongemma-26B-A4B-it at Q4_K_M is exactly 16,806,810,208 bytes (15.65 GiB / 16.81 GB) — an effective 5.207 bits per weight, not the nominal 4. Its KV cache at 32K is 1.54 GiB, not the 7.50 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
25.8B
total, not active
Architecture
diffusion-gemma
30 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K9.86 GiB10,590,000,8963.281DevQuasar
Q3_K_M12.38 GiB13,295,205,3764.119692DevQuasar
NVFP413.45 GiB14,439,362,0164.473FreedomAISVR
Q4_K_M15.65 GiB16,806,810,2085.207692unsloth
Q4_K_M15.65 GiB16,806,810,8805.207DevQuasar
Q5_K_M17.83 GiB19,145,543,2645.931692unsloth
Q5_K_M17.83 GiB19,145,543,9365.931DevQuasar
Q6_K21.10 GiB22,654,490,4647.018692unsloth
Q6_K21.10 GiB22,654,491,1367.018DevQuasar
Q8_025.03 GiB26,878,831,2008.327692unsloth
Q8_025.03 GiB26,878,831,8728.327DevQuasar
BF1647.07 GiB50,540,834,40015.657unsloth

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.45 GiB0.94 GiB2.09×5 / 25 / 0
8,1920.61 GiB1.88 GiB3.10×5 / 25 / 0
16,3840.92 GiB3.75 GiB4.09×5 / 25 / 0
32,7681.54 GiB7.50 GiB4.86×5 / 25 / 0
65,5362.79 GiB15.00 GiB5.37×5 / 25 / 0
131,0725.29 GiB30.00 GiB5.67×5 / 25 / 0

25 of 30 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 13.53 GiB. The real file is 15.65 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 7.50 GiB at 32K context where the real figure is 1.54 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

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

Questions people ask

How much VRAM does diffusiongemma-26B-A4B-it need?
Q4_K_M is exactly 16,806,810,208 bytes (15.65 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is diffusiongemma-26B-A4B-it's KV cache?
1.54 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.
Is diffusiongemma-26B-A4B-it a mixture-of-experts model?
Yes — 128 experts, null routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.
Which quantization of diffusiongemma-26B-A4B-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.