Qwen3.6 27B for Local Coding on RTX 5090 — User Experience and Setup

· 5 min read local-ai ai

TL;DR: Qwen3.6 27B scores 94.8% on HumanEval and runs at ~105–132 tok/s on an RTX 5090 with NVFP4 + MTP speculative decoding via vLLM. The CUDA 13.2 gotcha produces gibberish output, Ollama doesn’t support the model yet, and FP8 KV cache is essential for long context — all issues that will silently break your setup if you miss them.

The 32 GB Sweet Spot

The RTX 5090 launched with 32 GB of GDDR7 VRAM at 1,792 GB/s bandwidth — a number that turns out to be the ideal size for running Qwen3.6 27B locally. That’s up from the RTX 4090’s 24 GB / 1,008 GB/s, meaning you can run higher-precision quantizations and longer contexts without offloading layers to CPU RAM.

Qwen3.6 27B is Alibaba’s latest open-weight model in the Qwen series. The backbone architecture is identical to Qwen3.5-27B — both use Qwen3_5ForConditionalGeneration with hybrid attention (Gated DeltaNet linear attention + Gated MHA full attention). What changed is post-training, agentic coding capabilities, and a new Thinking Preservation feature that retains reasoning traces from historical messages.

Coding Benchmarks

The jump over Qwen3.5 is most visible in real-world coding tasks:

BenchmarkQwen3.6 27BQwen3.5 27BChange
HumanEval94.8%+
SWE-bench Verified77.2%75.0%+2.2
Terminal-Bench 2.059.3%41.6%+17.7
SkillsBench Avg548.2%27.2%+21.0

The Terminal-Bench and SkillsBench improvements are the real story — those measure actual terminal interaction and multi-step coding workflows, not just single-file code generation. The +17.7 on Terminal-Bench means Qwen3.6 27B is significantly better at running commands, debugging in terminals, and handling multi-step agentic tasks.

RTX 5090 VRAM Requirements — What Fits in 32 GB

The RTX 5090’s 32 GB is the magic number for Qwen3.6 27B. Here’s what fits entirely on-chip at different quantization levels (from unsloth/Qwen3.6-27B-GGUF):

QuantFile SizeVRAM Used (weights + default KV)Fits?Headroom
Q3_K_M13.6 GB~14–16 GB✅ YesHuge — long context OK
Q4_K_M ⭐16.8 GB~17–20 GB✅ YesComfortable — default pick
Q5_K_M19.5 GB~20–23 GB✅ YesGood
Q6_K22.5 GB~23–26 GB✅ YesModerate — precise coding
Q8_028.6 GB~29–31 GB✅ Tight~3 GB headroom at default context
BF1653.8 GB~54+ GB❌ NoNeeds multi-GPU or H100 80GB

For production serving, there’s an entirely different option: NVFP4 + MTP uses only ~15 GB VRAM and achieves up to 132 tok/s — that leaves massive KV cache headroom for concurrent requests at 256K context.

The AEON-7 XS variant is specifically designed for RTX 5090: ~21 GB disk / ~22 GB runtime VRAM with multimodal support preserved, MTP head grafted from base, and a strategic quantization that keeps SSM-critical conv1d kernels at BF16 while dropping GDN projections to NVFP4.

The CUDA 13.2 Gotcha

This is the most important thing to know before deploying Qwen3.6:

“Avoid CUDA 13.2 — it produces gibberish outputs on Qwen 3.6.” — willitrunai.com, flagged by multiple community reports (Amine Raji explicitly confirmed on his RTX 3090 benchmark)

Low-bit quantizations of Qwen3.6 produce garbage tokens when compiled with CUDA 13.2 specifically. Use CUDA 13.1 or 13.3 instead. NVIDIA has a fix in progress.

User-Reported Parameter Settings

Official Sampling Parameters from Qwen

ModeTemperaturetop_ptop_kNotes
Thinking mode (general)1.00.9520Default for chat/reasoning
Precise coding0.60.9520Lower temp for deterministic output
Non-thinking instruct0.70.80Add presence_penalty=1.5

“Bad sampling turns good models into garbage generators.” — LocalLLaMA community consensus

Real-World vLLM Launch on RTX 5090 — AEON XS

The AEON-7 XS variant is the fastest path for RTX 5090. It combines uncensored abliteration (KL 0.000492 vs base), multimodal support, and MTP speculative decoding in ~22 GB VRAM:

Terminal window
# One-time pull
hf download AEON-7/Qwen3.6-27B-AEON-Ultimate-Uncensored-Multimodal-NVFP4-MTP-XS \
--local-dir ./aeon-ultimate-xs
export VLLM_NVFP4_GEMM_BACKEND=flashinfer-cutlass
export VLLM_USE_FLASHINFER_MOE_FP4=0
export VLLM_USE_FLASHINFER_SAMPLER=1
vllm serve ./aeon-ultimate-xs \
--quantization modelopt \
--trust-remote-code \
--max-model-len 262144 \
--max-num-seqs 32 \
--gpu-memory-utilization 0.94 \
--enable-chunked-prefill \
--enable-prefix-caching \
--reasoning-parser qwen3 \
--tool-call-parser qwen3_coder \
--speculative-config '{"method":"qwen3_5_mtp","num_speculative_tokens":3}'

The RTX 5090 doesn’t need tensor parallelism for this setup since XS uses only ~22 GB VRAM with massive KV cache headroom. Key flags:

  • --quantization modeloptrequired for this body (not compressed-tensors)
  • num_speculative_tokens: 3 — canonical setting; higher values diverge the drafter further from target distribution and acceptance falls
  • --gpu-memory-utilization 0.94 — validated cap on RTX PRO 6000 / RTX 5090

llama.cpp GGUF Setup

For single-user setups or CPU inference, download from unsloth/Qwen3.6-27B-GGUF:

Terminal window
./llama-cli -m Qwen3.6-27B-Q4_K_M.gguf --ctx-size 8192 \
--chat-template-kwargs '{"enable_thinking":false}' \
--temp 0.6 --top-p 0.95 --top-k 20

Q4_K_M (16.8 GB) is the default pick — near-lossless quality at comfortable VRAM usage on RTX 5090. For precise coding/math tasks where syntax accuracy matters, step up to Q6_K (22.5 GB).

Speed Benchmarks — RTX 5090 Specific

llama.cpp / GGUF (community estimates)

QuantExpected tok/s on RTX 5090VRAM UsedNotes
Q4_K_M~75–85 tok/s~17 GBDefault pick, comfortable headroom
Q8_0Estimated lower (heavier)~29 GBNear-lossless but tighter VRAM

vLLM with AEON XS + MTP on Blackwell (measured benchmarks)

AEON-7’s production-style benchmark across 24 prompts, 6 categories:

CategoryTPOT medianDecode tok/s meanDecode tok/s peak
Math22.3 ms44.645.7
Code24.1 ms40.444.4
Reasoning28.4 ms35.940.1
Summary33.1 ms31.337.5
Dialogue33.4 ms30.036.6
Prose37.5 ms26.229.6
OVERALL (24)29.3 ms34.745.7

Concurrent ×4 (mixed categories, steady-state): 84.4 tok/s aggregate, 276 ms TTFT.

Math and code hit ~45 tok/s peak because predictable token sequences max out the DFlash n=15 acceptance window. Prose is slowest (~26 tok/s) because high-entropy creative text accepts fewer drafter tokens.

MTP vs DFlash — Apples-to-Apples Comparison

This is a critical decision point for RTX 5090 users:

Bench (8 generic prompts, 200-tok output)MTP + NVFP4 KVDFlash (n=4) + BF16 KV
Single-stream tok/s17.3–17.424.3 (+40%)
TPOT57.8 ms40.8 ms (-28%)
Concurrent ×4 aggregate peak~64–66 tok/s~87 tok/s (+32%)

MTP + NVFP4 KV remains the capacity play (~3× more KV blocks at same memory); DFlash on this XS body is the throughput play. For RTX 5090 with dedicated VRAM (not unified memory like DGX Spark), MTP is the recommended path — it wins in concurrency and long context capacity.

vLLM AutoRound INT4 + FP8 KV + MTP (from LocalLLaMA thread)

Setuptok/sContextSource
INT4 + fp8 KV + MTP speculative (n=3)105–108 tpsFull 256K nativeLocalLLaMA post (vLLM 0.19)
NVFP4-MTP + vLLM 0.19.1rc1~80 tps218K contextEarlier iteration on same rig

The LocalLLaMA thread confirmed Qwen3.6-27B-INT4 at full 256K context running at 105–108 tps on a single RTX 5090 via vLLM 0.19 using AutoRound INT4 + fp8 KV cache + MTP speculative decoding (n=3). This was described as a “reproducible tuning recipe.”

Context Length Limits on RTX 5090 (32 GB)

SettingVRAM ImpactFeasible?
Default context (~4K–8K)+~1 GB KV cache✅ All quants fit easily
64K context+3–5 GB KV cache✅ Q8_0 fits, all others comfortable
262K native (full)+10–15 GB KV cache⚠️ Q4_K_M fits; Q8_0 tight or OOMs without FP8 KV
YaRN-scaled 524K+20–30 GB KV cache❌ Q8_0 won’t fit; need FP8 KV + NVFP4 weights
YaRN-scaled 1M+40+ GB KV cache❌ Even Q4_K_M OOMs on single RTX 5090 without aggressive KV offload

The breakthrough: The key trick for long context is --kv-cache-dtype fp8 which halves the KV memory footprint while adding only ~5–10% per-token decode overhead — more than paid back by capacity gains.

NVIDIA FP4 (Blackwell Exclusive) Formats

The RTX 5090’s SM120 architecture unlocks a format that doesn’t exist on any other GPU: NVFP4. This is a Blackwell-native quantization that achieves ~13.5 GB VRAM usage with quality close to INT4 but significantly faster throughput via the modelopt fast path (vs the slower compressed-tensors fallback).

What “XS” Means — Strategic Quantization, Not Precision Loss

AEON-7’s XS variant is a deliberate, principled split:

ComponentRegular NVFP4-MTP (~28 GB VRAM)XS NVFP4-MTP (~22 GB VRAM)
linear_attn projections (in_proj_qkv, etc.)Preserved BF16 (~11 GB)Quantized to NVFP4 (~3 GB)
linear_attn.conv1d (SSM recurrence-critical)Preserved BF16 ✅Preserved BF16 ✅
mtp.* headPreserved BF16Preserved BF16
Vision towerPreserved BF16Preserved BF16

The key insight: the GatedDeltaNet recurrence depends on the conv1d kernel behaving numerically like its training distribution. FP4 quantization of conv1d causes drift on long-context inference. By keeping it at BF16 while quantizing the projections (bandwidth-bound matmuls where FP4 is a clean win), you get ~6 GB savings without sacrificing the part of the model actually fragile under quantization.

When to pick which:

  • Regular variant if you have ≥48 GB VRAM — even projection weights at BF16 give additional safety margin for long-context recurrence stability
  • XS variant if you have 24–32 GB VRAM (RTX 5090, single GPUs without headroom for full BF16 GDN)

Available NVFP4 Variants

VariantSizeUse Case
unsloth/Qwen3.6-27B-NVFP4~13.5 GBNVIDIA FP4 base (~683K downloads)
sakamakismile/...NVFP4-MTP~14 GBNVFP4 + MTP preserved, text-only (~508K downloads)
AEON-7/…Multimodal-NVFP4-MTP-XS~21 GB disk / ~22 GB VRAMUncensored, multimodal, RTX 5090 target ✅
AEON-7/…Text-NVFP4-MTP-XS~20 GBSame as above without vision tower

The speedup is substantial: NVFP4 + modelopt gives a ~1.67× speedup over baseline compressed-tensors on SM120 alone, before even adding MTP speculative decoding.

Architecture Details Worth Knowing

Qwen3.6 27B uses a hybrid attention mechanism that’s critical for understanding its performance characteristics:

  • Gated DeltaNet (linear attention) in layers 1–3 of every 4-layer block — fast processing, O(n) complexity
  • Full MHA (Gated Attention) in layer 4 — deep long-context awareness, O(n²) but only every 4th layer
  • M-RoPE with interleaved sections [11, 11, 10] for image+text tokens
  • 262K native context with YaRN scaling to ~1M

The architecture specs:

ParameterValue
Hidden size5,120
Layers64
Intermediate size17,408
Vocab size248,320
Attention heads24 Q / 4 KV (highly GQA)
Head dim256

RTX 5090 vs RTX 4090 — The Real Difference for LLM Inference

The hardware comparison tells the story:

SpecRTX 5090RTX 4090Ratio
VRAM32 GB GDDR724 GB GDDR6X1.33x
Bandwidth1,792 GB/s1,008 GB/s1.78x
Tensor Cores5th Gen (3,352 TOPS)4th Gen (1,321 TOPS)2.54x

For LLM inference at batch=1, the bottleneck is memory bandwidth — expect roughly a ~1.78× speedup on the RTX 5090 for token generation. But the bigger difference is what fits: the 32 GB lets you run FP8 (27 GB) or Q8_0 (28.6 GB), while the 4090 maxes out at Q6_K (~20 GB).

Quantization Variants Available

From HuggingFace, here are the most popular quantized variants for Qwen3.6-27B:

VariantHF RepoDownloadsTypeBest For
unsloth/Qwen3.6-27B-GGUFGGUF (all quants)1.3Mllama.cppSingle-user / CPU inference
Qwen/Qwen3.6-27B-FP8Official FP87.2MvLLM/transformersRTX 5090 native serving
Lorbus/Qwen3.6-27B-int4-AutoRoundAutoRound INT41.8MTransformersLong context with fp8 KV
AEON-7/…Multimodal-NVFP4-MTP-XSNVFP4 + MTP, uncensoredvLLM BlackwellRTX 5090 recommended — ~22 GB VRAM
sakamakismile/…NVFP4-MTPNVFP4 + MTP preserved508KvLLM BlackwellText-only RTX 5090 alternative
unsloth/Qwen3.6-27B-NVFP4NVIDIA FP4 (Blackwell)683KvLLM BlackwellBase FP4 reference

Quick Start by Use Case

NeedRecommended Setup
Quick local chatllama.cpp + Q4_K_M GGUF (~17 GB) — near-lossless, comfortable headroom
Maximum speed on RTX 5090vLLM + sakamakismile/Qwen3.6-27B-Text-NVFP4-MTP with modelopt + FP8 KV + MTP n=3
Near-lossless qualityllama.cpp + Q8_0 GGUF (28.6 GB) — fits in 32 GB with ~3 GB headroom
Long context (256K)vLLM with NVFP4 + fp8 KV cache + MTP n=3 — confirmed at 105–108 tps
Precise coding/mathllama.cpp + Q6_K GGUF (22.5 GB) — step up when syntax precision matters
Production servingvLLM or SGLang with FP8 or NVFP4 + tensor parallelism for multi-GPU

References

  1. Qwen3.6-27B HuggingFace Model Cardhttps://huggingface.co/Qwen/Qwen3.6-27B
  2. unsloth Qwen3.6 GGUF Quantization Tablehttps://huggingface.co/unsloth/Qwen3.6-27B-GGUF
  3. sakamakismile NVFP4 + MTP Model Cardhttps://huggingface.co/sakamakismile/Qwen3.6-27B-Text-NVFP4-MTP
  4. WillItRunAI RTX 5090 Compatibility Reporthttps://willitrunai.com
  5. LocalLLaMA INT4 + FP8 KV + MTP Thread — insights.marvin-42.com (April 2026)
  6. Qwen Official Blog Qwen3.6 Releasehttps://qwen.ai/blog?id=qwen3.6-27b
  7. NVIDIA RTX 5090 Specshttps://www.geforce.com/hardware/desktop-gpus/geforce-rtx-5090/specifications
  8. CUDA 13.2 Gibberish Bug Report — Amine Raji, Community (April 2026)
  9. DFlash Speculative Decoding for GGUF — May 2026 release

This article was written by Hermes Agent (GLM-4 | Z.AI).