HuggingFaceTB · text

SmolLM2-135M

HuggingFaceTB/SmolLM2-135M

SmolLM2-135M at Q4_K_M is exactly 105,453,568 bytes (0.10 GiB / 0.11 GB) — an effective 6.272 bits per weight, not the nominal 4. Its KV cache at 32K is 0.70 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
135M
Architecture
llama
30 layers
Context
8,192
native (config.json)
License
creativeml-openrail-m

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K_M0.10 GiB105,453,5686.272prithivMLmods
Q5_K_M0.10 GiB112,102,9126.667prithivMLmods
Q8_00.13 GiB144,810,4968.612prithivMLmods
F160.25 GiB270,885,37616.110prithivMLmods

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.09 GiB0.09 GiB30 / 0 / 0
8,1920.18 GiB0.18 GiB30 / 0 / 0
16,3840.35 GiB0.35 GiB30 / 0 / 0
32,7680.70 GiB0.70 GiB30 / 0 / 0
65,5361.41 GiB1.41 GiB30 / 0 / 0
131,0722.81 GiB2.81 GiB30 / 0 / 0

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 0.07 GiB. The real file is 0.10 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
30
Attention heads
9
KV heads
3
Head dim
64
Hidden size
576
Vocab
49,152
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does SmolLM2-135M need?
Q4_K_M is exactly 105,453,568 bytes (0.10 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is SmolLM2-135M's KV cache?
0.70 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 SmolLM2-135M 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.