Computed

MiniCPM5 1B on an Apple M3 Ultra (512GB)

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

Change the numbers →MiniCPM5 1B on every card Apple M3 Ultra (512GB) across every model

Verdict

Fits at FP16

384.0 GiB usable of 512 GB

Weights (Q4_K_M)

622 MiB

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

KV cache

24.0 KiB per token at FP16

24 layers × 2 KV heads × 128 dimensions

Speed ceiling

347 tok/s

819 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 Apple M3 Ultra (512GB). 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	131,072 (model cap)	347 tok/s
Q8_0	8.50	1.1 GiB	nominal	yes	131,072 (model cap)	607 tok/s
Q6_K	6.56	845 MiB	nominal	yes	131,072 (model cap)	753 tok/s
Q5_K_M	5.67	730 MiB	nominal	yes	131,072 (model cap)	847 tok/s
Q4_K_M	4.83	622 MiB	nominal	yes	131,072 (model cap)	959 tok/s
Q3_K_M	3.91	504 MiB	nominal	yes	131,072 (model cap)	1123 tok/s

What the context actually costs

The KV cache is 2 · layers · kv_heads · head_dim bytes per token per element — 2 · 24 · 2 · 128 · 2 B = 24.0 KiB. It depends on the key/value head count, not the attention-head count and not the parameter count. This model shares 2 KV heads across 16 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
4,096	96 MiB	48 MiB	718 MiB
8,192	192 MiB	96 MiB	814 MiB
32,768	768 MiB	384 MiB	1.4 GiB
131,072	3.0 GiB	1.5 GiB	3.6 GiB

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 Apple M3 Ultra (512GB) moves 819 GB/s, so the arithmetic ceiling is 347 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,080,632,832
Layers: 24
Attention / KV heads: 16 / 2
Head dimension: 128
Trained context: 131,072
Checkpoint as published: 2.0 GiB

Read from openbmb/MiniCPM5-1B. 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: 512 GB LPDDR5 unified
Bandwidth: 819 GB/s
Assumed usable: 75% → 384.0 GiB

Capacity and bandwidth from the vendor's specification. The usable fraction is an assumption, not a spec: unified memory is shared with the OS and the display, and the GPU working-set cap is raisable on Apple silicon with `sudo sysctl iogpu.wired_limit_mb`.

Questions this pairing answers

How much VRAM does MiniCPM5 1B need?

2.0 GiB for the weights at FP16 — 1.1B parameters at two bytes each — and 622 MiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 24.0 KiB per token of context, so 8,192 tokens costs a further 192 MiB. An Apple M3 Ultra (512GB) makes 384.0 GiB of its 512 GB available on the assumption below.

Can an Apple M3 Ultra (512GB) run MiniCPM5 1B?

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

How fast will MiniCPM5 1B run on an Apple M3 Ultra (512GB)?

No faster than 347 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 819 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 MiniCPM5 1B 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 24 layers and 2 key/value heads of 128 dimensions, shared across 16 query heads — grouped-query attention, which divides the cache by 8. That works out at 24.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 Apple M3 Ultra (512GB) →

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: 75% here, which is what this lane assumes for unified memory, where the OS and window server share the same pool — the other class assumes 92%, 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.