Computed

TinyLlama 1.1B Chat on an L40S

Yes — the unquantized weights fit with room for 2k tokens of context.

Change the numbers →TinyLlama 1.1B Chat on every card L40S across every model

Verdict

Fits at FP16

44.2 GiB usable of 48 GB

Weights (Q4_K_M)

633 MiB

2.0 GiB at FP16 · 1.1B params · 1 of 6 quant rows are measured files

KV cache

22.0 KiB per token at FP16

22 layers × 4 KV heads × 64 dimensions

Speed ceiling

385 tok/s

864 GB/s ÷ bytes read per token

Every quant, against this card

Weight bytes are the size of the real published file wherever one exists — 1 of these6 rows are measured from the published checkpoint, the rest computed from the parameter count. Max context is what the KV cache can grow to in whatever memory the weights leave behind, capped at the 2k tokens this model was trained to address.

Bars are the weight bytes at each precision; the dashed line is the usable memory of an L40S. Drawn from the computed byte counts, not sketched.

Precision	Bits/weight	Weights	Source	Fits	Max context	Ceiling
FP16 / BF16	16.00	2.0 GiB	measured file	yes	2,048 (model cap)	385 tok/s
Q8_0	8.50	1.1 GiB	nominal	yes	2,048 (model cap)	711 tok/s
Q6_K	6.56	860 MiB	nominal	yes	2,048 (model cap)	911 tok/s
Q5_K_M	5.67	744 MiB	nominal	yes	2,048 (model cap)	1046 tok/s
Q4_K_M	4.83	633 MiB	nominal	yes	2,048 (model cap)	1216 tok/s
Q3_K_M	3.91	513 MiB	nominal	yes	2,048 (model cap)	1480 tok/s

What the context actually costs

The KV cache is 2 · layers · kv_heads · head_dim bytes per token per element — 2 · 22 · 4 · 64 · 2 B = 22.0 KiB. It depends on the key/value head count, not the attention-head count and not the parameter count. This model shares 4 KV heads across 32 query heads, which divides the cache by 8 against multi-head attention.

Context	KV cache (FP16)	KV cache (8-bit)	Plus Q4_K_M weights

The speed ceiling, and where it comes from

Generating one token reads every active weight from memory once. At FP16 / BF16 that is 2.0 GiB, plus a pass over the KV cache. An L40S moves 864 GB/s (384-bit × 18 Gbps), so the arithmetic ceiling is 385 tok/s. Treat it as a bound, not an estimate: attention overhead, kernel launches and imperfect memory access keep real runtimes at roughly 60–80% of it, and nothing pushes past it.

Where these numbers come from

The model

Parameters: 1,100,048,384
Layers: 22
Attention / KV heads: 32 / 4
Head dimension: 64
Trained context: 2,048
Checkpoint as published: 2.0 GiB

Read from TinyLlama/TinyLlama-1.1B-Chat-v1.0. The parameter count is the Hub's own total over the tensor shapes, not a figure taken from the model's name.

The accelerator

Memory: 48 GB GDDR6 ECC
Bandwidth: 864 GB/s
Bus: 384-bit × 18 Gbps
Assumed usable: 92% → 44.2 GiB

Capacity and bandwidth from the vendor's specification. The bandwidth figure is checked against the bus width and data rate it derives from. The usable fraction is an assumption, not a spec: a driver context, compute workspace and any attached display come out of the same pool before a weight is loaded.

Questions this pairing answers

How much VRAM does TinyLlama 1.1B Chat need?

2.0 GiB for the weights at FP16 — 1.1B parameters at two bytes each — and 633 MiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 22.0 KiB per token of context, so 8,192 tokens costs a further 176 MiB. An L40S makes 44.2 GiB of its 48 GB available on the assumption below.

Can an L40S run TinyLlama 1.1B Chat?

Yes — the unquantized weights fit with room for 2k tokens of context. That is the weights and the KV cache together, against 44.2 GiB of usable memory.

How fast will TinyLlama 1.1B Chat run on an L40S?

No faster than 385 tokens/second at FP16 / BF16, and in practice below it. Decoding is memory-bound: every token reads all 2.0 GiB of weights plus the cache, and this card moves 864 GB/s. That division is the ceiling — no kernel, runtime or driver beats it, and a real runtime typically reaches 60–80% of it.

Why does the context length change how much memory TinyLlama 1.1B Chat needs?

Because the KV cache holds one key and one value vector per token, per layer, for the whole conversation, and it is allocated separately from the weights. This model has 22 layers and 4 key/value heads of 64 dimensions, shared across 32 query heads — grouped-query attention, which divides the cache by 8. That works out at 22.0 KiB per token. Parameter count tells you nothing about this number.

The same model on a different card

A different model on the same card

All 62 models on L40S →

Method and limits. Weight bytes are the byte size of the real published file wherever one exists, and the model's exact parameter count times the published llama.cpp bits-per-weight where it does not. That distinction is on every row above and it matters at both ends: a sub-1B model's Q4_K_M file runs a third larger than the nominal figure because k-quants keep its embedding tables at higher precision, and an already-4-bit release cannot be quantized upward at all. The KV cache is 2 · layers · kv_heads · head_dim · bytes per token, summed over layers with each sliding-window layer capped at its window. The speed figure is a roofline bound, not a benchmark: bandwidth divided by bytes read per token, which no runtime exceeds and every runtime falls short of. The usable fraction of card memory is an assumption: 92% here, which is what this lane assumes for a dedicated card — the other class assumes 75%, so it is not one number applied to every device. That is the only assumed input on this page; every other figure is computed from the model config and the card's published specification. Nothing on this page is written by a language model. Architecture from the model's published config, fetched 2026-08-07.