Qwen Vulkan PRs 28489 and 28501: below noise
I benchmark llama.cpp PR 28489 and PR 28501 with the 103.7 GiB Qwen3.8 Flash Next model on Strix Halo. Both are correct; neither is a production speed-up.
Field notes35 published
Every published investigation in date order. Use the Strix Halo and Storage pages when you want a shorter route into one subject.
Browse the archive
I benchmark llama.cpp PR 28489 and PR 28501 with the 103.7 GiB Qwen3.8 Flash Next model on Strix Halo. Both are correct; neither is a production speed-up.
I isolate five Qwen3.8 27B optimisations on Strix Halo. Two improve the current Vulkan stack; IQ4 main and TOP_K do not.
PR 28123 makes Qwen3.8 recurrent rollback practical for MTP. It removes a large copy cost, but does not make concurrent drafting safe.
PR 27941 fixes five Qwen3.8 state and QSA correctness faults. I would carry it into the next EVO-X3 canary, but not promote it untested.
PRs 28213 and 28244 gather QSA-selected K/V cells instead of masking the full cache. The long-context gains are real leads, not Vulkan results.
Issue 28280 records a Qwen3.8 prompt-cache checkpoint livelock on Strix Halo. Health alone can miss it, so slot progress needs watching.
Unsloth's six Qwen3.8 MTP GGUF sidecars range from 1.776 to 7.237 GiB. Shared Q8_0 is the sensible canary, not a production download.
A gfx1151 report shows Qwen3.8 draft-MTP content crossing between concurrent slots. That is a correctness blocker for my dual-slot service.
Merged PR 28190 makes Vulkan's Flash Attention dequant path engage before the KV cache is full. It is promising, not yet a 125B result.
An exact Strix Halo report measures 216 versus 406 prompt tokens/s from one llama.cpp lazy-mode switch. New canaries need it made explicit.
I upgraded EVO-X3 from a patched Lemonade 11.8 daemon to official 11.9. Fixed prefill held, decode moved -1.93% and every route passed.
I backported two merged llama.cpp Qwen fixes into the qualified Strix Halo runtime. One was 3–5% slower; the other lost the Vulkan device during model load.
I moved Qwen3.8 Flash Next to a Q8 dual-slot Vulkan 0.7.1 profile, measured 5–8% gains and passed a 30-minute cached concurrency soak.
I compare ROCm and Vulkan for Qwen3.8 Flash Next on AMD Strix Halo, then tune a 104GiB model to 15.6 tok/s single-stream and 24.3 tok/s aggregate.
I qualified a patched Vulkan build for Ornith 1.5 35B on Strix Halo, lifting 32K prefill by 24% and passing two 30-minute production soaks.
I repaired Qwen3.8 DFlash2 state reuse and a deterministic Vulkan stall, then deployed separate fast and exact 262K routes with memory-aware eviction.
Vulkan 0.6.10 fixes the long MTP stall on my Strix Halo machine, but Qwen3.6 decode falls about 11% and DeepSeek does not improve.
I compared Vulkan 0.6.2 and 0.6.4 with ROCm 7.14 on Strix Halo. The new release improved prefill by up to 72%, while decode performance stayed unchanged.
I ran 23 local coding-model deployments through 230 executable tasks on a 128GB Strix Halo workstation, comparing accuracy, latency and context limits.
Muse Glimmer 30B reaches 42 tok/s with DFlash on ROCm, but an 8K correctness test makes Vulkan the safer Strix Halo text route.
Matched before-and-after tests of llama.cpp, vLLM and Lemonade on Strix Halo, plus quantised KV, BF16, MTP, DFlash and ROCmFPX experiments.
Twenty matched SGLang-vLLM points plus llama.cpp and DeepSeek tests show why vLLM wins native Qwen while specialised runtimes win large quants.
Matched DeepSeek V4 Flash tests on Strix Halo show a 44% ROCm prefill gain from tuning, but patched Vulkan still wins all four llama.cpp workloads.
A tested route from EVO-X3 firmware settings to a signed Ubuntu USB image, 120 GiB dynamic GTT, SSH-key-only access, Lemonade and verified updates.
A measured DeepSeek V4 Flash 0731 study on Strix Halo: ROCm optimisation, a four-hour 32K thermal soak and 20 cold model loads.
A product-led examination of my Linux-based GMKtec EVO-X3: Strix Halo hardware, its provable firmware state and measured NVMe performance.
The Strix Halo stack I would keep after the first benchmark sequence: hardware, Linux memory, runtimes, models and operating controls.
A 101-minute, 165-request soak of Qwen3.5 122B at a nearly full 256K context, including throughput, memory, thermals and request-retention fixes.
A measured 0.8B-to-397B Strix Halo model sweep showing why file size, active parameters, context cost and answer quality must be separate decisions.
Matched llama.cpp benchmarks show why Strix Halo has no single fastest backend: ROCm wins prompt processing while Vulkan can win generation.
A measured Linux setup for ROCm on the Ryzen AI Max+ 395: memory, build provenance, model lifecycle, failure modes and a recovery runbook.
Benchmark parallel S3 ranged-download performance with s3bench, a Go tool for measuring throughput against AWS S3 and compatible object stores.
Build SPDK v26.05 and configure an NVMe over Fabrics target on Ubuntu with RDMA, explicit host access and a persistent JSON configuration.
Configure a persistent Linux NVMe over Fabrics target with RoCE, stable device identities, host access control and explicit network prerequisites.
A safety-first guide to inspecting and changing a supported NVMe LBA format, with separate notes on namespace management and secure erase.