Can I Run Ministral 3 on Beelink SER9 (Ryzen AI 9, 32 GB)?

Written by Jakub Rusinowski · Last updated September 6, 2026

Yes — comfortably

Yes, comfortably — Ministral 3 14B at Q8_0 needs about 17.1 GB of the 32 GB usable on Beelink SER9 (Ryzen AI 9, 32 GB), leaving ~14.9 GB spare and running at ~12 tok/s (estimated), with room for about 65,536 tokens of context.

Confidence: medium · Recommended quantization: Q8_0 · Estimated speed: ~12 tok/s

Buy This HardwareAMD Radeon RX 7900 XT 20GB — 20 GB VRAM · 315 W board power Deploy in the Cloud NowRTX 4090 on RunPod — from $0.34/hr · rate checked 2026-07

or compare on Vast.ai from $0.35/hr (typical low · varies)

As an Amazon Associate we earn from qualifying purchases. Cloud GPU links are referral links — we may earn a commission at no extra cost to you.

Beelink SER9 (Ryzen AI 9, 32 GB) — what it gives a model

Usable memory for models	32 GB
Memory bandwidth	256 GB/s
Form factor	Mini PC
Operating system	Windows or Linux
Memory upgradeable	Yes
Price	$859 (lib/data/ai-stations.ts (street price), checked 2026-07-06)

Ministral 3 on Beelink SER9 (Ryzen AI 9, 32 GB): memory by quantization

Quant	Memory needed	Fits 32 GB?	Max context	Est. speed	Download
F16	30.2 GB	✓ Yes	16K	~6.6 tok/s	28 GB
Q8_0	17.1 GB	✓ Yes	64K	~12 tok/s	14.9 GB
Q6_K	13.7 GB	✓ Yes	64K	~15.2 tok/s	11.5 GB
Q5_K_M	12.1 GB	✓ Yes	64K	~17.4 tok/s	9.9 GB
Q4_K_M	10.6 GB	✓ Yes	128K	~20.1 tok/s	8.5 GB
Q3_K_M	8.1 GB	✓ Yes	128K	~27.1 tok/s	6 GB
Q2_K	6.8 GB	✓ Yes	128K	~33.6 tok/s	4.6 GB

Which Ministral 3 sizes fit

Variant	Needs at Q4_K_M	Fits?	Est. speed
Ministral 3 14B	10.6 GB	✓ Fits	~20.1 tok/s
Ministral 3 8B	6.8 GB	✓ Fits	~32.9 tok/s
Ministral 3 3B	3.5 GB	✓ Fits	~72.1 tok/s

What to watch out for

This model does not publish its full attention configuration, so the KV-cache share of these figures is inferred from its parameter count rather than computed exactly.

Beelink SER9 32 GB limitations

Shares system memory with the iGPU, so the usable model budget is well below the nominal 32 GB.
Memory bandwidth, not capacity, is the limit here — expect single-digit tokens/sec on large models.

Recommended setup

Ollama or llama.cpp (CUDA/ROCm) — vLLM if you need concurrent serving

How these numbers are calculated

Memory need = quantized weights + KV cache at 8,192 tokens (f16) + 0.8 GB runtime overhead.
32 GB unified memory at 256 GB/s, shared between CPU and GPU.
Throughput is a memory-bandwidth roofline estimate, not a measurement. It is labelled "estimated" everywhere it appears.
KV cache is inferred from the parameter count because this model does not publish its full attention configuration.

FAQ