# Qwen 35B-A3B MoE vs 27B dense in local coding tests: ~4× faster, much smaller quality gap than I expected — retained record

> Retained reddit record from reddit:LocalLLaMA.

Canonical: https://highsignal.app/data/records/f647e93ace0eb834

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:LocalLLaMA)  published 2026-08-08 05:44 ingested 2026-08-08 06:58

[original source ↗](https://www.reddit.com/r/LocalLLaMA/comments/1vinr66/qwen_35ba3b_moe_vs_27b_dense_in_local_coding/)

## retained text



```
<!-- SC_OFF --><div class="md"><p>I compared Qwen 35B-A3B MoE against Qwen 27B dense on a series of local coding-maintenance tasks. On my R9700/llama.cpp setup, the MoE model generated about <strong>3.9× faster (~116 vs ~30 tok/s)</strong>, but the coding-quality difference was much smaller than I expected.</p> <p>Both usually handled ordinary bug fixes and multi-file changes correctly. As I made the tests progressively harder, the dense model did show an advantage—but mainly in <strong>implicit invariants, unusual edge cases, and consequences beyond the literal request</strong>, rather than basic correctness.</p> <p><strong>Models</strong></p> <ul> <li>Qwen 3.6 35B-A3B — Q5_K_M (MoE)</li> <li>Qwen 3.6 27B BASE — Q4_K_XL (dense)</li> </ul> <p><strong>Hardware/runtime</strong></p> <ul> <li>Radeon AI PRO R9700 32 GB</li> <li>Ryzen 9 5950X</li> <li>llama.cpp, Vulkan, full GPU offload</li> <li>8K context for these coding tests</li> </ul> <p>One early controlled parser-repair test is illustrative:</p> <ul> <li><strong>35B-A3B:</strong> ~116 tok/s, provisional score 7/10</li> <li><strong>27B dense:</strong> ~30 tok/s, provisional score 7/10</li> </ul> <p>That single result isn't my argument by itself. I subsequently moved through progressively harder multi-file tests involving imports, stable IDs, collision handling, data preservation, and eventually references that had to remain valid when IDs were remapped.</p> <p>My takeaway so far is deliberately narrow: <strong>on these tasks, the ~4× throughput difference was much larger than the practical coding-quality difference I observed.</strong></p> <p>This is a small local experiment, not a universal claim about MoE vs dense architectures. The quantizations also differ, so I wouldn't pretend this is an academically controlled architecture comparison. But the results do make me skeptical of treating <strong>active parameter count as a straightforward proxy for practical capability</strong>.</p> <p>I have the original prompts, source fixtures, exact llama.cpp commands, raw terminal transcripts, and the progressively harder integration tests. I'll put more methodology and examples in a comment below if anyone wants to dig into the details.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/WSTangoDelta"> /u/WSTangoDelta </a> <br /> <span><a href="https://www.reddit.com/r/LocalLLaMA/comments/1vinr66/qwen_35ba3b_moe_vs_27b_dense_in_local_coding/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/LocalLLaMA/comments/1vinr66/qwen_35ba3b_moe_vs_27b_dense_in_local_coding/">[comments]</a></span>
```



document fetched 2026-08-08 06:58 · canonical https://reddit.com/r/LocalLLaMA/comments/1vinr66/qwen_35ba3b_moe_vs_27b_dense_in_local_coding
