Skip to main content

Lab · LLM VRAM · SmolLM

Computed

SmolLM2 360M Instruct memory requirements

362M parameters — 690 MiB of weights at FP16, 258 MiB at Q4_K_M, and 40.0 KiB of KV cache per token on top. Solved against 22 real accelerators; 22 of them can hold it.

Parameters

362M

361,821,120 exactly

Weights, Q4_K_M

258 MiB

690 MiB unquantized

KV cache

40.0 KiB

per token · 32L × 5 KV × 64

Smallest card (Q4)

8 GB

Jetson Orin Nano Super (8GB)

Weights at each precision

PrecisionBits/weightWeightsSourceNotes
FP16 / BF1616.00690 MiBmeasured fileUnquantized. Two bytes per parameter, exactly.
Q8_08.54369 MiBmeasured fileEffectively lossless; the usual reference point for quantized quality.
Q6_K8.12350 MiBmeasured fileQuality loss is hard to measure on most benchmarks.
Q5_K_M6.41277 MiBmeasured fileA middle point when Q4 fits with too little room for context.
Q4_K_M5.98258 MiBmeasured fileThe default choice for local inference — the best size/quality knee.
Q3_K_M5.19224 MiBmeasured fileMeasurable quality loss. Worth it only to make a model fit at all.

Every accelerator

Largest quant that fits with at least 4k of context, the context it leaves, and the bandwidth ceiling on decode speed. Each row links to the worked page for that pairing.

AcceleratorMemoryBandwidthBest quantMax contextCeiling
Apple M3 Ultra (512GB)512 GB819 GB/sFP16 / BF168,192773 tok/s
H200 141GB (SXM)141 GB4800 GB/sFP16 / BF168,1924532 tok/s
Apple M4 Max (128GB)128 GB546 GB/sFP16 / BF168,192515 tok/s
H100 80GB (SXM5)80 GB3350 GB/sFP16 / BF168,1923163 tok/s
A100 80GB (SXM)80 GB2039 GB/sFP16 / BF168,1921925 tok/s
Jetson AGX Orin (64GB)64 GB204.8 GB/sFP16 / BF168,192193 tok/s
RTX 6000 Ada Generation48 GB960 GB/sFP16 / BF168,192906 tok/s
L40S48 GB864 GB/sFP16 / BF168,192816 tok/s
Apple M4 Pro (48GB)48 GB273 GB/sFP16 / BF168,192258 tok/s
A100 40GB (SXM)40 GB1555 GB/sFP16 / BF168,1921468 tok/s
GeForce RTX 509032 GB1792 GB/sFP16 / BF168,1921692 tok/s
GeForce RTX 409024 GB1008 GB/sFP16 / BF168,192952 tok/s
Radeon RX 7900 XTX24 GB960 GB/sFP16 / BF168,192906 tok/s
GeForce RTX 309024 GB936 GB/sFP16 / BF168,192884 tok/s
Apple M4 (24GB)24 GB120 GB/sFP16 / BF168,192113 tok/s
GeForce RTX 508016 GB960 GB/sFP16 / BF168,192906 tok/s
GeForce RTX 5070 Ti16 GB896 GB/sFP16 / BF168,192846 tok/s
GeForce RTX 4080 SUPER16 GB736 GB/sFP16 / BF168,192695 tok/s
GeForce RTX 4070 Ti SUPER16 GB672 GB/sFP16 / BF168,192634 tok/s
GeForce RTX 4060 Ti 16GB16 GB288 GB/sFP16 / BF168,192272 tok/s
GeForce RTX 3060 12GB12 GB360 GB/sFP16 / BF168,192340 tok/s
Jetson Orin Nano Super (8GB)8 GB102 GB/sFP16 / BF168,19296 tok/s

Questions about this model

How much VRAM does SmolLM2 360M Instruct need?

690 MiB for the weights at FP16 and 258 MiB at Q4_K_M, from an exact count of 361,821,120 parameters. On top of that, the KV cache costs 40.0 KiB per token of context — 320 MiB at 8k and 1.3 GiB at 32k.

What is the smallest GPU that runs SmolLM2 360M Instruct?

Of the 22 accelerators here, the smallest that holds Q4_K_M weights is the Jetson Orin Nano Super (8GB) at 8 GB — 258 MiB of weights against 6.0 GiB usable, leaving room for 8k tokens. For unquantized weights you need at least a Jetson Orin Nano Super (8GB).

Why is the KV cache for SmolLM2 360M Instruct the size it is?

Because it stores one key and one value vector per token, per layer: 32 layers × 5 KV heads × 64 dimensions × 2 (K and V) × 2 bytes = 40.0 KiB per token. Grouped-query attention shares those 5 KV heads across 15 query heads, cutting the cache by 3× against multi-head attention. None of this can be read off the parameter count.

Compare with

Method and limits. The parameter count and every architecture figure on this page are read from the model's own published config and the Hub's index over its tensor shapes, fetched 2026-08-07 — nothing here is recalled from a model's name. Weight bytes are the size of a real published file wherever one exists and the parameter count times the published llama.cpp bits-per-weight where it does not; every row says which. Speed figures are roofline bounds — memory bandwidth divided by bytes read per token — not benchmarks. Nothing on this page is written by a language model.