r/LocalLLaMAMay 4, 2026, 06:16 UTC+8

Pushing a 5-Year-Old 6GB VRAM Laptop to Its Limits: Qwen3.6-35B-A3B

Pushing a 5-Year-Old 6GB VRAM laptop to Its Limits: Qwen3.6-35B-A3B

Reddit user abhinand05 ran Qwen3.6-35B-A3B on a 5-year-old Asus ROG Zephyrus G14, reaching about 23 t/s plugged in and 10+ t/s unplugged. The setup uses RTX 2060 Max-Q 6GB, 24GB DDR4, Ryzen 7, plus llama-server configs for 64k and 128k context. The key detail is the mix of CPU MoE, KV-cache quantization, and ngram speculative decoding.

Why it matters: HKR-H/K/R all pass: the old-laptop angle is clicky, the post gives speeds and configs, and local-LLM cost resonates. It remains a single Reddit run, not a broader release.

Read the original ↗Export Markdown

Take

A 6GB VRAM laptop running Qwen3.6-35B-A3B at about 23 t/s punches a hole in the “wait for new GPUs” story. The disclosed box is modest: a 5-year-old Zephyrus G14, RTX 2060 Max-Q 6GB, 24GB DDR4, and Ryzen 7. The point is not the 35B label. It is the stack: A3B MoE activation, CPU MoE, KV-cache quantization, and ngram speculative decoding splitting the bottleneck.

I would not sell this as normal-user-ready. Reddit is 403-blocked here, so the body does not show quant format, batch size, prompt length, sampling settings, or power curve. The summary mentions llama-server configs for 64k and 128k context, which already says this is closer to a llama.cpp tuner flex than an Ollama-style one-click 7B run. It proves the local inference ceiling is software-sensitive; it does not prove the setup cost disappeared.

Source: r/LocalLLaMA · reddit.com
Published: May 4, 2026, 06:16 UTC+8 · May 4, 2026