Can I Run OLMo 2 on Beelink SER9 (Ryzen AI 9, 32 GB)?
Written by Jakub Rusinowski · Last updated November 26, 2024
Yes — comfortably
Yes, comfortably — OLMo 2 13B Instruct at Q8_0 needs about 22.1 GB of the 32 GB usable on Beelink SER9 (Ryzen AI 9, 32 GB), leaving ~9.9 GB spare and running at ~5 tok/s (estimated), with room for about 4,096 tokens of context.
Confidence: high · Recommended quantization: Q8_0 · Estimated speed: ~5 tok/s
See what else this hardware can run →
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 | 120 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) |
OLMo 2 on Beelink SER9 (Ryzen AI 9, 32 GB): memory by quantization
| Quant | Memory needed | Fits 32 GB? | Max context | Est. speed | Download |
|---|---|---|---|---|---|
| F16 | 34.9 GB | ✗ No | — | — | 27.4 GB |
| Q8_0 | 22.1 GB | ✓ Yes | 4K | ~5 tok/s | 14.6 GB |
| Q6_K | 18.7 GB | ✓ Yes | 4K | ~6.1 tok/s | 11.2 GB |
| Q5_K_M | 17.2 GB | ✓ Yes | 4K | ~6.8 tok/s | 9.7 GB |
| Q4_K_M | 15.8 GB | ✓ Yes | 4K | ~7.6 tok/s | 8.3 GB |
| Q3_K_M | 13.4 GB | ✓ Yes | 4K | ~9.6 tok/s | 5.8 GB |
| Q2_K | 12 GB | ✓ Yes | 4K | ~11.2 tok/s | 4.5 GB |
Which OLMo 2 sizes fit
| Variant | Needs at Q4_K_M | Fits? | Est. speed |
|---|---|---|---|
| OLMo 2 13B Instruct | 15.8 GB | ✓ Fits | ~7.6 tok/s |
| OLMo 2 7B Instruct | 9.5 GB | ✓ Fits | ~13.3 tok/s |
What to watch out for
- Context is capped at about 4,096 tokens before memory runs out, which is short for document or agent work.
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 120 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 computed from this model's published attention configuration.
FAQ
Can I run OLMo 2 on Beelink SER9 (Ryzen AI 9, 32 GB)?
Yes, comfortably — OLMo 2 13B Instruct at Q8_0 needs about 22.1 GB of the 32 GB usable on Beelink SER9 (Ryzen AI 9, 32 GB), leaving ~9.9 GB spare and running at ~5 tok/s (estimated), with room for about 4,096 tokens of context.
Which quantization of OLMo 2 should I use on Beelink SER9 (Ryzen AI 9, 32 GB)?
Q8_0 — it needs about 22.1 GB of the 32 GB available, downloads as roughly 14.6 GB, and runs at an estimated 5 tokens/sec with up to 4K of context.
What limits OLMo 2 on Beelink SER9 (Ryzen AI 9, 32 GB)?
Nothing binding — the model fits with headroom and generates at a usable speed on this hardware.
Which runtime should I use?
Ollama or llama.cpp (CUDA/ROCm) — vLLM if you need concurrent serving
Other Computers
Other Models on Beelink SER9 (Ryzen AI 9, 32 GB)
- Phi 3.5 Family on Beelink SER9 (Ryzen AI 9, 32 GB)
- Phi-4 Family on Beelink SER9 (Ryzen AI 9, 32 GB)
- Phi-4 Mini on Beelink SER9 (Ryzen AI 9, 32 GB)
- Poolside Laguna XS 2.1 on Beelink SER9 (Ryzen AI 9, 32 GB)
- Qwen 2.5 Family on Beelink SER9 (Ryzen AI 9, 32 GB)
OLMo 2 on GPUs
- OLMo 2 on NVIDIA GeForce RTX 5080
- OLMo 2 on NVIDIA GeForce RTX 5070 Ti
- OLMo 2 on NVIDIA GeForce RTX 5060 Ti 16GB
- OLMo 2 on NVIDIA GeForce RTX 5060 Ti 8GB