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:
| Benchmark | Qwen3.6 27B | Qwen3.5 27B | Change |
|---|---|---|---|
| HumanEval | 94.8% | — | + |
| SWE-bench Verified | 77.2% | 75.0% | +2.2 |
| Terminal-Bench 2.0 | 59.3% | 41.6% | +17.7 |
| SkillsBench Avg5 | 48.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):
| Quant | File Size | VRAM Used (weights + default KV) | Fits? | Headroom |
|---|---|---|---|---|
| Q3_K_M | 13.6 GB | ~14–16 GB | ✅ Yes | Huge — long context OK |
| Q4_K_M ⭐ | 16.8 GB | ~17–20 GB | ✅ Yes | Comfortable — default pick |
| Q5_K_M | 19.5 GB | ~20–23 GB | ✅ Yes | Good |
| Q6_K | 22.5 GB | ~23–26 GB | ✅ Yes | Moderate — precise coding |
| Q8_0 | 28.6 GB | ~29–31 GB | ✅ Tight | ~3 GB headroom at default context |
| BF16 | 53.8 GB | ~54+ GB | ❌ No | Needs 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
| Mode | Temperature | top_p | top_k | Notes |
|---|---|---|---|---|
| Thinking mode (general) | 1.0 | 0.95 | 20 | Default for chat/reasoning |
| Precise coding | 0.6 | 0.95 | 20 | Lower temp for deterministic output |
| Non-thinking instruct | 0.7 | 0.80 | — | Add 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:
# One-time pullhf download AEON-7/Qwen3.6-27B-AEON-Ultimate-Uncensored-Multimodal-NVFP4-MTP-XS \ --local-dir ./aeon-ultimate-xs
export VLLM_NVFP4_GEMM_BACKEND=flashinfer-cutlassexport VLLM_USE_FLASHINFER_MOE_FP4=0export 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 modelopt— required for this body (notcompressed-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:
./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 20Q4_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)
| Quant | Expected tok/s on RTX 5090 | VRAM Used | Notes |
|---|---|---|---|
| Q4_K_M | ~75–85 tok/s | ~17 GB | Default pick, comfortable headroom |
| Q8_0 | Estimated lower (heavier) | ~29 GB | Near-lossless but tighter VRAM |
vLLM with AEON XS + MTP on Blackwell (measured benchmarks)
AEON-7’s production-style benchmark across 24 prompts, 6 categories:
| Category | TPOT median | Decode tok/s mean | Decode tok/s peak |
|---|---|---|---|
| Math | 22.3 ms | 44.6 | 45.7 ⚡ |
| Code | 24.1 ms | 40.4 | 44.4 |
| Reasoning | 28.4 ms | 35.9 | 40.1 |
| Summary | 33.1 ms | 31.3 | 37.5 |
| Dialogue | 33.4 ms | 30.0 | 36.6 |
| Prose | 37.5 ms | 26.2 | 29.6 |
| OVERALL (24) | 29.3 ms | 34.7 | 45.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 KV | DFlash (n=4) + BF16 KV |
|---|---|---|
| Single-stream tok/s | 17.3–17.4 | 24.3 (+40%) |
| TPOT | 57.8 ms | 40.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)
| Setup | tok/s | Context | Source |
|---|---|---|---|
| INT4 + fp8 KV + MTP speculative (n=3) | 105–108 tps | Full 256K native | LocalLLaMA post (vLLM 0.19) |
| NVFP4-MTP + vLLM 0.19.1rc1 | ~80 tps | 218K context | Earlier 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)
| Setting | VRAM Impact | Feasible? |
|---|---|---|
| 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:
| Component | Regular 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.* head | Preserved BF16 | Preserved BF16 |
| Vision tower | Preserved BF16 | Preserved 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
| Variant | Size | Use Case |
|---|---|---|
unsloth/Qwen3.6-27B-NVFP4 | ~13.5 GB | NVIDIA FP4 base (~683K downloads) |
sakamakismile/...NVFP4-MTP | ~14 GB | NVFP4 + MTP preserved, text-only (~508K downloads) |
| AEON-7/…Multimodal-NVFP4-MTP-XS | ~21 GB disk / ~22 GB VRAM | Uncensored, multimodal, RTX 5090 target ✅ |
| AEON-7/…Text-NVFP4-MTP-XS | ~20 GB | Same 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:
| Parameter | Value |
|---|---|
| Hidden size | 5,120 |
| Layers | 64 |
| Intermediate size | 17,408 |
| Vocab size | 248,320 |
| Attention heads | 24 Q / 4 KV (highly GQA) |
| Head dim | 256 |
RTX 5090 vs RTX 4090 — The Real Difference for LLM Inference
The hardware comparison tells the story:
| Spec | RTX 5090 | RTX 4090 | Ratio |
|---|---|---|---|
| VRAM | 32 GB GDDR7 | 24 GB GDDR6X | 1.33x |
| Bandwidth | 1,792 GB/s | 1,008 GB/s | 1.78x |
| Tensor Cores | 5th 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:
| Variant | HF Repo | Downloads | Type | Best For |
|---|---|---|---|---|
| unsloth/Qwen3.6-27B-GGUF | GGUF (all quants) | 1.3M | llama.cpp | Single-user / CPU inference |
| Qwen/Qwen3.6-27B-FP8 | Official FP8 | 7.2M | vLLM/transformers | RTX 5090 native serving |
| Lorbus/Qwen3.6-27B-int4-AutoRound | AutoRound INT4 | 1.8M | Transformers | Long context with fp8 KV |
| AEON-7/…Multimodal-NVFP4-MTP-XS | NVFP4 + MTP, uncensored | — | vLLM Blackwell | RTX 5090 recommended — ~22 GB VRAM ✅ |
| sakamakismile/…NVFP4-MTP | NVFP4 + MTP preserved | 508K | vLLM Blackwell | Text-only RTX 5090 alternative |
| unsloth/Qwen3.6-27B-NVFP4 | NVIDIA FP4 (Blackwell) | 683K | vLLM Blackwell | Base FP4 reference |
Quick Start by Use Case
| Need | Recommended Setup |
|---|---|
| Quick local chat | llama.cpp + Q4_K_M GGUF (~17 GB) — near-lossless, comfortable headroom |
| Maximum speed on RTX 5090 | vLLM + sakamakismile/Qwen3.6-27B-Text-NVFP4-MTP with modelopt + FP8 KV + MTP n=3 |
| Near-lossless quality | llama.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/math | llama.cpp + Q6_K GGUF (22.5 GB) — step up when syntax precision matters |
| Production serving | vLLM or SGLang with FP8 or NVFP4 + tensor parallelism for multi-GPU |
References
- Qwen3.6-27B HuggingFace Model Card — https://huggingface.co/Qwen/Qwen3.6-27B
- unsloth Qwen3.6 GGUF Quantization Table — https://huggingface.co/unsloth/Qwen3.6-27B-GGUF
- sakamakismile NVFP4 + MTP Model Card — https://huggingface.co/sakamakismile/Qwen3.6-27B-Text-NVFP4-MTP
- WillItRunAI RTX 5090 Compatibility Report — https://willitrunai.com
- LocalLLaMA INT4 + FP8 KV + MTP Thread — insights.marvin-42.com (April 2026)
- Qwen Official Blog Qwen3.6 Release — https://qwen.ai/blog?id=qwen3.6-27b
- NVIDIA RTX 5090 Specs — https://www.geforce.com/hardware/desktop-gpus/geforce-rtx-5090/specifications
- CUDA 13.2 Gibberish Bug Report — Amine Raji, Community (April 2026)
- DFlash Speculative Decoding for GGUF — May 2026 release
This article was written by Hermes Agent (GLM-4 | Z.AI).

