functiongemma-270m-it
google/functiongemma-270m-itfunctiongemma-270m-it at Q4_K_M is exactly 253,127,392 bytes (0.24 GiB / 0.25 GB) — an effective 7.553 bits per weight, not the nominal 4. Its KV cache at 32K is 0.11 GiB, not the 0.56 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| UD-IQ2_XXS | 0.17 GiB | 179,748,064 | 5.364 | — | unsloth |
| UD-IQ2_M | 0.17 GiB | 182,430,944 | 5.444 | — | unsloth |
| UD-IQ3_XXS | 0.17 GiB | 184,161,504 | 5.495 | — | unsloth |
| IQ2_M | 0.22 GiB | 234,797,792 | 7.006 | — | bartowski |
| IQ3_XXS | 0.22 GiB | 235,985,632 | 7.042 | — | bartowski |
| Q3_K_S | 0.22 GiB | 236,722,912 | 7.064 | — | bartowski |
| Q3_K_S | 0.22 GiB | 236,723,424 | 7.064 | — | unsloth |
| Q2_K | 0.22 GiB | 237,091,552 | 7.075 | — | bartowski |
| Q2_K_L | 0.22 GiB | 237,091,552 | 7.075 | — | bartowski |
| IQ3_XS | 0.22 GiB | 237,091,552 | 7.075 | — | bartowski |
| Q2_K | 0.22 GiB | 237,092,064 | 7.075 | — | unsloth |
| Q2_K_L | 0.22 GiB | 237,092,064 | 7.075 | — | unsloth |
| IQ3_M | 0.22 GiB | 239,006,432 | 7.132 | — | bartowski |
| IQ4_XS | 0.22 GiB | 240,870,112 | 7.188 | — | bartowski |
| IQ4_XS | 0.22 GiB | 240,870,624 | 7.188 | — | unsloth |
| Q4_0 | 0.22 GiB | 241,586,912 | 7.209 | — | bartowski |
| Q4_0 | 0.22 GiB | 241,587,424 | 7.209 | — | unsloth |
| IQ4_NL | 0.23 GiB | 241,976,032 | 7.221 | — | bartowski |
| Q3_K_M | 0.23 GiB | 241,976,032 | 7.221 | — | bartowski |
| Q3_K_M | 0.23 GiB | 241,976,544 | 7.221 | — | unsloth |
| IQ4_NL | 0.23 GiB | 241,976,544 | 7.221 | — | unsloth |
| Q3_K_L | 0.23 GiB | 246,399,712 | 7.353 | — | bartowski |
| Q4_1 | 0.23 GiB | 247,689,952 | 7.391 | — | bartowski |
| Q4_1 | 0.23 GiB | 247,690,464 | 7.391 | — | unsloth |
| Q4_K_S | 0.23 GiB | 249,901,792 | 7.457 | — | bartowski |
| Q4_K_S | 0.23 GiB | 249,902,304 | 7.457 | — | unsloth |
| Q4_K_L | 0.24 GiB | 253,127,392 | 7.553 | — | bartowski |
| Q4_K_M | 0.24 GiB | 253,127,392 | 7.553 | — | bartowski |
| Q4_K_M | 0.24 GiB | 253,127,904 | 7.553 | — | unsloth |
| Q5_K_S | 0.24 GiB | 258,011,872 | 7.699 | — | bartowski |
| Q5_K_S | 0.24 GiB | 258,012,384 | 7.699 | — | unsloth |
| Q5_K_M | 0.24 GiB | 260,039,392 | 7.760 | — | bartowski |
| Q5_K_L | 0.24 GiB | 260,039,392 | 7.760 | — | bartowski |
| Q5_K_M | 0.24 GiB | 260,039,904 | 7.760 | — | unsloth |
| Q6_K | 0.26 GiB | 282,987,232 | 8.444 | — | bartowski |
| Q6_K_L | 0.26 GiB | 282,987,232 | 8.444 | — | bartowski |
| Q6_K | 0.26 GiB | 282,987,744 | 8.444 | — | unsloth |
| Q8_0 | 0.27 GiB | 291,557,792 | 8.700 | — | ggml-org |
| Q8_0 | 0.27 GiB | 291,558,112 | 8.700 | — | bartowski |
| Q8_0 | 0.27 GiB | 291,558,624 | 8.700 | — | unsloth |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.03 GiB | 0.07 GiB | 2.67× | 3 / 15 / 0 |
| 8,192 | 0.04 GiB | 0.14 GiB | 3.69× | 3 / 15 / 0 |
| 16,384 | 0.06 GiB | 0.28 GiB | 4.57× | 3 / 15 / 0 |
| 32,768 | 0.11 GiB | 0.56 GiB | 5.19× | 3 / 15 / 0 |
| 65,536 | 0.20 GiB | 1.13 GiB | 5.57× | 3 / 15 / 0 |
| 131,072 | 0.39 GiB | 2.25 GiB | 5.77× | 3 / 15 / 0 |
15 of 18 layers cache only a 512-token window rather than the full context, on a period of 6. Figures assume the default configuration; --swa-full disables the saving entirely.
Compare with
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 0.14 GiB. The real file is 0.24 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 0.56 GiB at 32K context where the real figure is 0.11 GiB, because most of this model's layers cache a fixed window rather than the whole context.
Architecture
Questions people ask
- How much VRAM does functiongemma-270m-it need?
- Q4_K_M is exactly 253,127,392 bytes (0.24 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
- How large is functiongemma-270m-it's KV cache?
- 0.11 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 functiongemma-270m-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.