Oct 13, 2026
Summary
First-party source: https://howquant.dev/benchmarks/strix-halo-rocm-vs-vulkan/ (published 2026-08-24, updated 2026-09-16; native measurement date not explicitly given). This is historical source recovery, not a new run. The author says raw JSON is retained privately, not publicly downloadable; these are published summary cells, not independently inspected raw runs.
Model Qwen3.8-27B Q8_0, filename Qwen3.8-27B-Q8_0.gguf, 27.3B parameters. Author-reported disk file size 29,105,393,664 bytes is not resident memory. CRITICAL HF provenance: The pinned bartowski reference matches publisher, model, quant and filename, but has 29,116,388,960 bytes versus the author-reported tested file 29,105,393,664 bytes. Therefore this is not verified historical byte identity; the model card reports later reuploads. Historical revision and hash unknown. Verified pinned reference: https://huggingface.co/bartowski/Qwen3.8-27B-GGUF/blob/44e6f088cbf95fffb83ec2564f30e63b26cd187e/Qwen3.8-27B-Q8_0.gguf . No weights downloaded.
Hardware: Corsair AI Workstation 300, AMD Ryzen AI Max+ 395 / Radeon 8060S gfx1151, 128 GiB unified RAM (source explicitly GiB; not dedicated VRAM), Balanced power mode. Ubuntu 24.04.4 LTS, kernel 6.18.36-061836-generic. Source reports memory 8000 MT/s configured/8532 measured; method for measured speed unspecified. Official SKU specifications are 16 CPU cores, 32 hardware threads and 40 graphics CUs, not measured active counts: https://www.amd.com/en/products/processors/laptop/ryzen/ai-300-series/amd-ryzen-ai-max-plus-395.html . Native benchmark thread count unknown; do not borrow server --threads 14.
GPU quantity 1 is bound to Vulkan by https://howquant.dev/guides/vulkan-compute-strix-halo/#runtime-device-selection : author explicitly identifies one real GPU plus CPU software llvmpipe, retained native JSON devices: auto, and run attributed to Radeon 8060S. This is author-reported campaign evidence; raw JSON is not public. Same author's eGPU experiments are distinct and are not added to this run. ROCm companion guide shows sole ROCm0 on the machine but not independently per-run count; HIP cells are retained as companion evidence only.
Qualified headline and all Vulkan values, tok/s: pp512 278.80 ±9.40; pp2048 268.30 ±0.20; pp8192 254.20 ±0.10; tg128 7.77 ±0.00; pg2048+256 55.18 ±0.01. Same-backend PP512/TG128 headline; never pair HIP prefill with Vulkan generation. Reported SD 0.00 is rounded, not proof of zero variability. Source-reported HIP companion rates (GPU count not independently bound to each run): pp512 341.30 ±12.40; pp2048 322.80 ±0.60; pp8192 303.60 ±0.20; tg128 7.76 ±0.00; pg2048+256 58.30 ±0.03.
Runtime llama.cpp c060ca974, build 10603; Vulkan RADV/Mesa 26.1.7. Exact native commands use -ngl 999 -b 2048 -ub 512 -fa on -r 5; plain decoding, no speculation even if filename says MTP. Native PP sizes 512/2048/8192 are timed synthetic work, not maximum context capacity. TG128 is 128 sequential synchronized random-token decode work units, not delivered text. Exact timer checked: https://github.com/ggml-org/llama.cpp/blob/c060ca974/tools/llama-bench/llama-bench.cpp . Per-repetition rate=(n_prompt+n_gen)/elapsed; mean and sample SD across 5. Model load/warmup precede timer; KV cleared before each repetition; no pre-existing depth. Separate requested contexts 512/2048/8192 for PP and 128 for TG; PG requests 2304 and times 2048+256 together. Effective allocated capacity unknown. PG rate is not separate PP, TG or client E2E. F16 K/V and enabled warmup derive from exact command and historical defaults.
No measured TTFT, first-content latency, resident memory, model-load latency or client throughput is submitted. SPEED-Bench coding/MTP values and its configured 131072 context are a separate client/server workload with different timing; excluded from these native fields. No native long-context claim is taken from that server capacity. LlamaPerf structured rates are rounded to 0.1 tokens/s to match form precision; exact source means and SDs are retained above.