Qalarc / Platform

Strix Halo for local AI — measured, and corrected where we were wrong

By Alexei Brown, Qalarc (Sydney) · GMKtec EVO-X2 AI · Ryzen AI Max+ 395 · 128GB LPDDR5X-8000 · verified 2026-09-11 · llms.txt
Strix Halo (Ryzen AI Max+ 395 + Radeon 8060S, 256 GB/s unified memory) is the best price-per-token platform for sparse-MoE models: we measure 48-52 tok/s daily. It is not a dense-70B platform — 3-5 tok/s, a number we once overstated by 5-6× and corrected publicly. Every claim below is measured on our box or sourced.

The platform, plainly

AMD Strix Halo = Ryzen AI Max+ 395 (16 Zen 5 cores) fused with the Radeon 8060S iGPU (gfx1151, RDNA 4, 40 compute units) on quad-channel LPDDR5X-8000 — 256 GB/s of unified memory, up to 128GB. Our unit: a GMKtec EVO-X2 AI (~$1,999 class) with 128GB, running Ollama on ROCm. It is the machine behind every benchmark on this site.

What actually runs well (measured, our box)

ClassExample (measured)SpeedVerdict
Sparse MoE 30B-classGLM 4.7 Flash (30B-A3B)48.0 tok/s✅ The sweet spot
Sparse MoE 35B-classOrnith 1.5 35B-A3B52.4 tok/s✅ Fastest big model here
Small dense 7-14BOrnith 9B, Llama 3.2 3B31.8-120 tok/s✅ Instant
Mid dense ~32BQwen3.8 27B10.7 tok/s⚠️ Usable, patience required
Large dense 70BLlama 70B Q43-5 tok/s❌ Not a 70B platform

The correction we publish on purpose

Early bandwidth math suggested 25-30 tok/s for 70B Q4 on Strix Halo. Reality: 3-5 tok/s. We were wrong by 5-6× and corrected it publicly — bandwidth arithmetic (256 GB/s ÷ 37GB = ~7 passes/s) is the theoretical ceiling, and GPU inference lands well under it. Any Strix Halo review quoting 25+ tok/s on dense 70B is repeating our old mistake.

Strix Halo vs the field (70B Q4, third-party + measured)

SystemPriceMemory70B speed
Strix Halo (ours)~$1,999128GB unified3-5 t/s
NVIDIA DGX Spark$3,999128GB unified~5 t/s
Mac Studio M4 Ultra$7,000192GB20-25 t/s (est.)
RTX 4090 (offload)$1,60024GB + CPU60-80 t/s (est., hybrid)
H100 80GB$30,000+80GB25 t/s (pure GPU)

The punchline: at 2× the price, DGX Spark buys software maturity, not dense-model speed. And none of these beat the real answer on this platform — don't run dense 70B locally at all; run MoE.

Why MoE is Strix Halo's killer feature

Generation is bandwidth-bound: speed ≈ bandwidth ÷ bytes-moved-per-token. A 30B-A3B MoE moves ~3B parameters per token; a 27B dense moves 27B. Same 256 GB/s: 4.5× the speed for similar capability class. This is why our daily driver is GLM 4.7 Flash (48 tok/s) rather than any dense model.

Configuration notes from our box

VRAM carve: 32GB UMA — Q4 30B-class fits fully in VRAM (100% GPU residency measured) with system RAM to spare. Runtime: Ollama 0.33 on ROCm 7.2; the 0.18→0.33 upgrade alone lifted GLM 4.7 Flash from ~38 to 48 tok/s — re-benchmark after every runtime update. Context: prefill decays from 830 tok/s (840-token prompt) to 217 tok/s at 25k — keep chat loops under ~8k and use deep context only for retrieval. Concurrency: two sessions at 34.3 tok/s each — parallel agents are nearly free.

Who should buy one

Buy Strix Halo if you want one quiet desk-side box for MoE chat/agents + image generation + everyday computing at ~$2k. Skip it if your workload is dense 70B+ — that's Mac Studio Ultra, multi-GPU, or API territory.

The measured LLM comparison Local Model Atlas AI-OS