Huge thanks for the Qwen3-Coder-Next GGUFs πŸ™

#30
by urbanswelt - opened

Just wanted to drop a quick appreciation post β€” your
Qwen3-Coder-Next-GGUF
release has turned my homelab into a genuine local-coding-agent platform.
Specifically running the UD-Q8_K_XL quant.

My setup

  • AMD Ryzen AI Max+ 395 ("Strix Halo") β€” integrated Radeon 8060S, 128 GiB
    unified LPDDR5X memory
  • Fedora + ROCm 7.2.2 toolbox (kyuz0/amd-strix-halo-toolboxes)
  • llama.cpp in router mode via --models-preset (multi-model dropdown)
  • Quant: Qwen3-Coder-Next-UD-Q8_K_XL (~80 GiB, 3 shards)
  • Context: full 262144 native, no quality compromise

Performance β€” exceeds your published expectations

Your model card says: "If your quant fully fits on your device, expect 20+
tokens/s."
On my Strix Halo box with the UD-Q8_K_XL quant, I'm seeing:

Test Result
Single-stream tg128 36.72 t/s
Sustained tg at 64k context 36.6 t/s (no degradation)
Prompt processing (4k context) 668 t/s
4 parallel agents, 4k prompt + 256 gen each 76 t/s aggregate
8 parallel streams, small batches 102 t/s aggregate

So ~80% above your minimum expectation β€” and that's because the MoE
architecture (3B active out of 80B total) plays perfectly with this
platform's unified memory and integrated GPU. My measured memory bandwidth is
~217 GB/s (about 85% of theoretical), and a dense 80B model on this box would
crawl at maybe 2.5 t/s. Qwen3-Coder-Next runs 15Γ— faster than a dense
model of equivalent quality would.

This is exactly the design promise from your release notes β€” "Super
Efficient with Significant Performance: With only 3B activated parameters
(80B total), it achieves performance comparable to models with 10–20Γ— more
active parameters"
β€” verified empirically on commodity hardware.

What's been excellent about your release specifically

Unsloth Dynamic 2.0 quants are noticeably better than vanilla quants at
the same file size. The UD- variants' selective bit allocation means I can
run Q8_K_XL and trust quality stays near-lossless. The third-party Aider /
LiveCodeBench / MMLU Pro benchmarks you link are genuinely useful β€” choosing
a quant from your repo doesn't feel like a coin flip.

The chat template fixes are not a small thing. With --jinja in
llama.cpp, tool-calling and the full 256k context "just work" β€” I tested 4
parallel coding-agent-style requests (4k context each, 256 token generation)
and they ran without any template wrangling. That's the kind of polish that
turns a model release into a usable product.

The model card and runbook are top-tier. Quant size guidance, hardware
requirements, sampling parameters, the docs.unsloth.ai run guide β€” I went
from "haven't tried this model" to running it in production-mode on novel
hardware in maybe 30 minutes. Compare that to the usual hours of figuring
out which quant to download and what flags to set.

Bottom line

Strix Halo gives me the memory pool. llama.cpp gives me the runtime. Your
quants give me the model that actually runs fast and produces good output
.
All three pieces have to be good for the result to be good β€” and yours
delivers above the spec sheet.

For anyone else considering this combo: Qwen3-Coder-Next UD-Q8_K_XL on an
AMD Strix Halo (128 GiB) box is a serious local coding agent platform
. 36
t/s single-stream, scales to 4 concurrent agents at 19 t/s each, full 256k
context, no thermal throttling under sustained load. With the right toolbox
the setup is straightforward.

Keep doing what you're doing. The Dynamic 2.0 work in particular is one of
those quiet contributions that makes the entire local LLM ecosystem better.

Thanks again πŸ™

Sign up or log in to comment