Just the best model πŸ’˜ as always Qwen Team is number 1 πŸ₯° .

#51
by auf1r2 - opened

Just facts:

  1. I can run 170Gb Q6_K_XL on a single Strix Halo 128Gb mini PC 20t/s TG, 300+ t/s PP (no MTP) ~ thanks to new LLM architecture
  2. It beats every other local model of that size in coding. Very clever model, you can delegate it some work and it won't stuck like other models can do.
  3. Default xhigh settings for reasoning is clever decision, it may start slowly but if you calculate total time to delivering fully functional code - it is faster! Other "fast" models are fast to deliver garbage but if you try to deliver fully functional code - Qwen3.8 FN on XHigh settings is faster! (I'm talking about real project production code, not funny 1 HTML test apps, but it's good for them too)

Love Qwen models, cheers to Qwen Team for contributing local AI community πŸ₯‚

Hi, can you share how you managed to run Q6_K_M. I am having hard time to go beyond Q3_k_XL from unsloth. I am on windows.

I'm using Ubuntu 26.04 on Strix Halo

Set 64GB VRAM + 64GB RAM in BIOS

Ubuntu params for Grub (/etc/default/grub): GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=off amdgpu.gttsize=61440 amdgpu.ppfeaturemask=0xffffffff pcie_aspm=off nvme_core.default_ps_max_latency_us=0 pcie_port_pm=off amdgpu.gpu_recovery=1 amdgpu.lockup_timeout=60000 amdgpu.cik_support=0 amdgpu.si_support=0 rocm_debug=0" (after editing you need to call sudo update-grub -> restart) <<--- This tells OS to use some Strix Halo optimizations + allows it to use 64 + 60 = 124 GB of memory for VRAM.

Install amd-ttm -> run amd-ttm --set 60 then restart.

then command to run llama-server:
./llama-server --model "/home/xxx/EvoX2/LLMs/models/unsloth/Qwen3.8-Flash-Next-GGUF-Q6/Qwen3.8-Flash-Next-UD-Q6_K_XL-00001-of-00006.gguf" --host 192.168.1.xx --port 8080 --tools get_info --cors-origins 192.168.1.xx --api-key xxx --jinja --n-gpu-layers all --n-cpu-moe 0 --parallel 1 --no-kv-unified --kv-offload --load-mode mmap --spec-type none --fit off --flash-attn on --cache-type-k q8_0 --cache-type-v q8_0 --ctx-size 163840 --batch-size 2048 --ubatch-size 2048 --no-op-offload --override-tensor "per_layer_token_embd=CPU" --lazy-mode on --temperature 1.0 --top-k 20 --repeat-penalty 1.00 --presence-penalty 0.0 --top-p 0.95 --min-p 0.0 --reasoning on --chat-template-kwargs '{"reasoning_effort":"xhigh"}' --reasoning-preserve

Clever trick, thanks for the tips! It helped me step up to Q4_K_XL. I'm on Windows and use this machine for work, so switching to Ubuntu or allocating the entire 124 GB of RAM isn't an option. Still, with your optimizations, getting Q4_K_XL running is a great result. Appreciate it!

Just facts:

  1. I can run 170Gb Q6_K_XL on a single Strix Halo 128Gb mini PC 20t/s TG, 300+ t/s PP (no MTP) ~ thanks to new LLM architecture
  2. It beats every other local model of that size in coding. Very clever model, you can delegate it some work and it won't stuck like other models can do.
  3. Default xhigh settings for reasoning is clever decision, it may start slowly but if you calculate total time to delivering fully functional code - it is faster! Other "fast" models are fast to deliver garbage but if you try to deliver fully functional code - Qwen3.8 FN on XHigh settings is faster! (I'm talking about real project production code, not funny 1 HTML test apps, but it's good for them too)

Love Qwen models, cheers to Qwen Team for contributing local AI community πŸ₯‚

Can endorse this. Running the Intel/Qwen3.8-Flash-Next-W4A16-AutoRound quant and been absolutely stunned how good the model is in doing what you tell it to do. The throughput is amazing as well due to the small number of activate params and being able to run the important stuff only on VRAM (with the n-gram-table offload). Sometimes it feels like it can almost read your mind. Feeling very Opus-like, in some tasks even better. I really cannot wait for the Qwen4-family releases – in hopes that they would release an even better trained checkpoint than this with the same architecture!!

Sign up or log in to comment