Qwen3.6 27B looks fast locally, but agent reliability is mixed

Qwen3.6 27B was tested as a for coding-agent work on a high-end personal machine. On a 9800X3D, 64GB memory, and RTX 5090 setup, careful llama.cpp tuning produced 6,454 logged samples across roughly 20 hours of mixed coding-agent, debugging, and documentation work. The average speed was 140.7 , the median was 134.9 , the most common range was 120 to 130 , and some samples reached 233 .

The setup used q8 KV cache, 192k context, MTP draft=10, spec-draft-p-min=0.5, and batch/ubatch 512. The wider experience around Qwen3.6 27B is not uniform. Some results show strong speed and good single-prompt output, while other report unreliable behavior with compared with BF16, or weaker real task performance than larger Qwen 3.5 models.

Other tests show high FP8 throughput on an RTX 6000 Ada with vLLM, and one local coding setup finished an for a Java test game, though it took a long time. There is also a cost-efficiency concern that multilingual ability may waste model capacity for developers who only need English coding help.

Key points

  • On an RTX 5090 setup, Qwen3.6 27B reached 140.7 average and 134.9 median .
  • The measurement came from about 20 hours of real coding-agent, debugging, and documentation work, not just a short demo.
  • MTP and q8 KV cache settings helped speed, but llama.cpp cache handling can still show warnings for this model.
  • may be fast and smaller, but some were less reliable than BF16.
  • The practical cost question is task success rate, retry count, and hardware cost, not alone.

Sources covering this story (7)

Read original