Computed

Gemma 3 27B Instruct on an A100 80GB (SXM)

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

Change the numbers →Gemma 3 27B Instruct on every card A100 80GB (SXM) across every model

Verdict

Fits at FP16

73.6 GiB usable of 80 GB

Weights (Q4_K_M)

15.4 GiB

51.1 GiB at FP16 · 27.4B params · 1 of 6 quant rows are measured files

KV cache

496.0 KiB per token at FP16

62 layers × 16 KV heads × 128 dimensions

Speed ceiling

36 tok/s

2039 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 128k tokens this model was trained to address.

Bars are the weight bytes at each precision; the dashed line is the usable memory of an A100 80GB (SXM). Drawn from the computed byte counts, not sketched.

Precision	Bits/weight	Weights	Source	Fits	Max context	Ceiling
FP16 / BF16	16.00	51.1 GiB	measured file	yes	131,072 (model cap)	36 tok/s
Q8_0	8.50	27.1 GiB	nominal	yes	131,072 (model cap)	67 tok/s
Q6_K	6.56	20.9 GiB	nominal	yes	131,072 (model cap)	86 tok/s
Q5_K_M	5.67	18.1 GiB	nominal	yes	131,072 (model cap)	99 tok/s
Q4_K_M	4.83	15.4 GiB	nominal	yes	131,072 (model cap)	115 tok/s
Q3_K_M	3.91	12.5 GiB	nominal	yes	131,072 (model cap)	140 tok/s

What the context actually costs

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

Sliding-window attention. 52 of this model's 62 layers attend to a 1,024-token window and stop growing there; only the remaining 10 keep scaling with context. That is why the cache figures below flatten out — and why a calculator that ignores the layer pattern over-states this model's long-context footprint several times over.

Context	KV cache (FP16)	KV cache (8-bit)	Plus Q4_K_M weights
4,096	736 MiB	368 MiB	16.1 GiB
8,192	1.0 GiB	528 MiB	16.5 GiB
32,768	2.9 GiB	1.5 GiB	18.3 GiB
131,072	10.4 GiB	5.2 GiB	25.8 GiB

The speed ceiling, and where it comes from

Generating one token reads every active weight from memory once. At FP16 / BF16 that is 51.1 GiB, plus a pass over the KV cache. An A100 80GB (SXM) moves 2039 GB/s, so the arithmetic ceiling is 36 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: 27,432,406,640
Layers: 62
Attention / KV heads: 32 / 16
Head dimension: 128
Trained context: 131,072
Checkpoint as published: 51.1 GiB

Read from unsloth/gemma-3-27b-it — an ungated mirror of google/gemma-3-27b-it, whose own config cannot be fetched without an access token. 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: 80 GB HBM2e
Bandwidth: 2039 GB/s
Assumed usable: 92% → 73.6 GiB

Capacity and bandwidth from the vendor's specification. 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 Gemma 3 27B Instruct need?

51.1 GiB for the weights at FP16 — 27.4B parameters at two bytes each — and 15.4 GiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 496.0 KiB per token of context on its full-attention layers, so 8,192 tokens costs a further 1.0 GiB. An A100 80GB (SXM) makes 73.6 GiB of its 80 GB available on the assumption below.

Can an A100 80GB (SXM) run Gemma 3 27B Instruct?

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

How fast will Gemma 3 27B Instruct run on an A100 80GB (SXM)?

No faster than 36 tokens/second at FP16 / BF16, and in practice below it. Decoding is memory-bound: every token reads all 51.1 GiB of weights plus the cache, and this card moves 2039 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 Gemma 3 27B Instruct 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 62 layers and 16 key/value heads of 128 dimensions, shared across 32 query heads — grouped-query attention, which divides the cache by 2. That works out at 496.0 KiB per token, except that 52 of the 62 layers use a 1024-token sliding window and stop growing there. 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 A100 80GB (SXM) →

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. This checkpoint also carries a vision tower; its parameters are inside the totals above because they load whether or not you send it an image.