Qwen3.6 35B-A3B Runs Fast on 780M iGPU
💡35B MoE blasts 282 t/s on laptop iGPU—game-changer for local inference
⚡ 30-Second TL;DR
What Changed
282.40 pp/s at 1024 prompt length on Vulkan
Why It Matters
Proves large 35B MoE models viable on laptop iGPUs, lowering barriers for local AI experimentation. Boosts adoption of AMD hardware in LLM inference.
What To Do Next
Benchmark Qwen3.6-35B-A3B Q6_K on your AMD iGPU using llama.cpp Vulkan.
Key Points
- •282.40 pp/s at 1024 prompt length on Vulkan
- •20.74 tg/s at 128 tokens generation
- •Runs Q6_K on Radeon 780M with 64GB DDR5 RAM
- •llama.cpp master build with ngl=99 layers offloaded
- •Requires GTT and hang timeout kernel tweaks
🧠 Deep Insight
AI-generated analysis for this event — not the original article.
🔑 Enhanced Key Takeaways
- •The Qwen3.6 series utilizes a novel 'Active-3-Base' (A3B) Mixture-of-Experts architecture, which dynamically routes tokens through only 3 billion parameters per forward pass, significantly reducing the VRAM footprint compared to dense 35B models.
- •The performance gains on the Radeon 780M are largely attributed to recent upstream patches in llama.cpp that optimize Vulkan memory management for unified memory architectures, specifically addressing the overhead of GTT (Graphics Translation Table) mapping.
- •Community testing indicates that while the 780M iGPU can handle the Q6_K quantization, the bottleneck shifts to system memory bandwidth (DDR5-5600/6400), making high-speed RAM essential for maintaining the reported 20 tg/s generation speed.
📊 Competitor Analysis▸ Show
| Model | Architecture | VRAM Requirement (Q6_K) | Typical iGPU Performance |
|---|---|---|---|
| Qwen3.6 35B-A3B | MoE (3B active) | ~28 GB | ~20 tg/s (780M) |
| Mistral-Nemo 12B | Dense | ~10 GB | ~35 tg/s (780M) |
| Llama-3.1 8B | Dense | ~7 GB | ~45 tg/s (780M) |
🛠️ Technical Deep Dive
- •Model Architecture: Qwen3.6 35B-A3B uses a sparse MoE design where the total parameter count is 35B, but only 3B parameters are active per token, allowing it to fit into system RAM while providing the reasoning capabilities of a much larger model.
- •Vulkan Implementation: The llama.cpp Vulkan backend utilizes the 'VK_KHR_buffer_device_address' extension to minimize CPU-GPU synchronization overhead.
- •Kernel Tweaks: The 'GTT' (Graphics Translation Table) adjustment involves increasing the
i915.enable_gttor equivalent AMDamdgpu.gttsizeparameter in the Linux kernel boot arguments to allow the iGPU to map larger portions of system RAM as VRAM. - •Quantization: The Q6_K (6-bit) quantization format provides a balance between perplexity retention and memory bandwidth utilization, which is critical for iGPU performance where memory bus width is the primary constraint.
🔮 Future ImplicationsAI analysis grounded in cited sources
⏳ Timeline
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: Reddit r/LocalLLaMA ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.