KAT Coder V2.5 Dev memory requirements

34.7B parameters — 64.6 GiB of weights at FP16, 19.5 GiB at Q4_K_M, and 80.0 KiB of KV cache per token on top. Solved against 22 real accelerators; 15 of them can hold it.

Open the calculator →All models

Parameters

34.7B

34,660,610,688 exactly

Weights, Q4_K_M

19.5 GiB

64.6 GiB unquantized

KV cache

80.0 KiB

per token · 40L × 2 KV × 256

Smallest card (Q4)

24 GB

GeForce RTX 4090

Weights at each precision

Precision	Bits/weight	Weights	Source	Notes
FP16 / BF16	16.00	64.6 GiB	measured file	Unquantized. Two bytes per parameter, exactly.
Q8_0	8.50	34.3 GiB	nominal	Effectively lossless; the usual reference point for quantized quality.
Q6_K	6.56	26.5 GiB	nominal	Quality loss is hard to measure on most benchmarks.
Q5_K_M	5.67	22.9 GiB	nominal	A middle point when Q4 fits with too little room for context.
Q4_K_M	4.83	19.5 GiB	nominal	The default choice for local inference — the best size/quality knee.
Q3_K_M	3.91	15.8 GiB	nominal	Measurable 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.

Accelerator	Memory	Bandwidth	Best quant	Max context	Ceiling
Apple M3 Ultra (512GB)	512 GB	819 GB/s	FP16 / BF16	262,144	128 tok/s
H200 141GB (SXM)	141 GB	4800 GB/s	FP16 / BF16	262,144	752 tok/s
Apple M4 Max (128GB)	128 GB	546 GB/s	FP16 / BF16	262,144	86 tok/s
H100 80GB (SXM5)	80 GB	3350 GB/s	FP16 / BF16	118,430	525 tok/s
A100 80GB (SXM)	80 GB	2039 GB/s	FP16 / BF16	118,430	320 tok/s
Jetson AGX Orin (64GB)	64 GB	204.8 GB/s	Q8_0	179,598	55 tok/s
RTX 6000 Ada Generation	48 GB	960 GB/s	Q8_0	129,266	259 tok/s
L40S	48 GB	864 GB/s	Q8_0	129,266	233 tok/s
Apple M4 Pro (48GB)	48 GB	273 GB/s	Q8_0	22,312	74 tok/s
A100 40GB (SXM)	40 GB	1555 GB/s	Q8_0	32,797	420 tok/s
GeForce RTX 5090	32 GB	1792 GB/s	Q6_K	38,931	595 tok/s
GeForce RTX 4090	24 GB	1008 GB/s	Q4_K_M	33,958	421 tok/s
Radeon RX 7900 XTX	24 GB	960 GB/s	Q4_K_M	33,958	401 tok/s
GeForce RTX 3090	24 GB	936 GB/s	Q4_K_M	33,958	391 tok/s
Apple M4 (24GB)	24 GB	120 GB/s	Q3_K_M	29,137	58 tok/s
GeForce RTX 5080	16 GB	960 GB/s	no fit	—	—
GeForce RTX 5070 Ti	16 GB	896 GB/s	no fit	—	—
GeForce RTX 4080 SUPER	16 GB	736 GB/s	no fit	—	—
GeForce RTX 4070 Ti SUPER	16 GB	672 GB/s	no fit	—	—
GeForce RTX 4060 Ti 16GB	16 GB	288 GB/s	no fit	—	—
GeForce RTX 3060 12GB	12 GB	360 GB/s	no fit	—	—
Jetson Orin Nano Super (8GB)	8 GB	102 GB/s	no fit	—	—

Questions about this model

How much VRAM does KAT Coder V2.5 Dev need?

64.6 GiB for the weights at FP16 and 19.5 GiB at Q4_K_M, from an exact count of 34,660,610,688 parameters. On top of that, the KV cache costs 80.0 KiB per token of context — 640 MiB at 8k and 2.5 GiB at 32k.

What is the smallest GPU that runs KAT Coder V2.5 Dev?

Of the 22 accelerators here, the smallest that holds Q4_K_M weights is the GeForce RTX 4090 at 24 GB — 19.5 GiB of weights against 22.1 GiB usable, leaving room for 33k tokens. For unquantized weights you need at least an H100 80GB (SXM5).

Why is the KV cache for KAT Coder V2.5 Dev the size it is?

Because it stores one key and one value vector per token, per layer: 40 layers × 2 KV heads × 256 dimensions × 2 (K and V) × 2 bytes = 80.0 KiB per token. Grouped-query attention shares those 2 KV heads across 16 query heads, cutting the cache by 8× 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.