reddit.com via Reddit

Qwen 3.6-27B MTP delivers 16% speed boost on Windows

inference open source local-inference mtp-benchmarks windows-ai

Key insights

  • Qwen 3.6-27B with MTP on Windows Strix Halo achieves 14.5 tok/s versus 12.5 tok/s baseline, a confirmed 16% throughput gain.
  • Prefill speed showed no regression with MTP enabled, resolving the primary concern that had discouraged users from activating the feature.
  • These are the first published MTP benchmarks for Strix Halo on Windows, extending previously Linux-only data to the broader desktop install base.

Why this matters

Local inference practitioners on Windows have had to take Linux benchmark numbers on faith when evaluating whether MTP is worth enabling; this data closes that gap with hardware-matched comparisons. AMD Strix Halo is positioned as a high-memory-bandwidth consumer platform for large local models, and confirming MTP compatibility on Windows strengthens its case against Apple Silicon for Windows-native AI developers. The prefill-regression question was a real adoption blocker, and its public resolution via reproducible benchmarks will likely accelerate MTP uptake across the llama.cpp user base.

Summary

Qwen 3.6-27B Dense with Multi-Token Prediction enabled now has its first Windows benchmark numbers, and the results land squarely in line with what Linux users have seen on AMD Strix Halo hardware. A developer running llama.cpp on Windows with Strix Halo recorded a baseline of 12.5 tokens per second, climbing to 14.5 tok/s with MTP active. That 16% single-stream gain held across coding and writing tasks, extending a benchmark dataset that had previously been Linux-exclusive and confirming that the Windows runtime path isn't leaving performance on the table. Essentially: (Qwen, llama.cpp, AMD) now have a cross-platform MTP story that removes the Linux-or-nothing constraint for local inference practitioners. - Prefill speed showed no regression with MTP on, which had been the main blocker keeping cautious users from enabling it. - The results position Strix Halo as a verified MTP-capable platform on both major desktop operating systems. - The 16% gain applies in single-stream scenarios; multi-stream and batched workload numbers remain unpublished. For the growing segment of Windows-based local inference users, this removes one of the last practical reasons to dual-boot or virtualize Linux for high-throughput Qwen deployments.

Potential risks and opportunities

Risks

  • llama.cpp MTP implementation is still in active development; a future update that regresses Windows performance could invalidate adoption decisions made on the basis of this single benchmark.
  • AMD Strix Halo driver updates for Windows have historically introduced memory-bandwidth regressions; users enabling MTP at scale may hit throughput drops before any official fix lands.
  • Community benchmarks without controlled methodology can propagate inflated expectations, and if reproducibility fails on different Strix Halo SKUs or RAM configurations, trust in the llama.cpp Windows ecosystem takes a credibility hit.

Opportunities

  • llama.cpp-adjacent tooling vendors (LM Studio, Jan, Ollama) can now confidently surface MTP as a recommended default toggle for Windows Strix Halo users, improving their out-of-box performance story.
  • AMD has a concrete, third-party-validated benchmark to reference in Strix Halo marketing to the local AI developer segment, reinforcing its positioning against Apple M-series in the prosumer inference market.
  • Benchmark infrastructure providers and hobbyist hardware reviewers (e.g., Tom's Hardware, ServeTheHome) can expand local LLM test suites to include MTP variants now that a reproducible Windows baseline exists.

What we don't know yet

  • Whether the 16% single-stream gain holds under concurrent or batched inference loads on the same Strix Halo hardware, which would affect multi-user and agent-loop use cases.
  • No driver or llama.cpp version pinning was published alongside the benchmark, making exact reproduction uncertain as both move quickly in mid-2026.
  • Whether competing high-memory-bandwidth Windows platforms (Intel Lunar Lake, Qualcomm Snapdragon X Elite) show comparable MTP gains or hardware-specific regressions.

Originally reported by reddit.com

Read the original article →

Original headline: r/LocalLLaMA: Qwen 3.6-27B Dense With MTP on Strix Halo Windows — First Windows Benchmarks Show ~16% Throughput Gain Over Baseline