Qwen 3.6 Q2-FP8 Terminal Bench 2 and GPQA Scores

Reddit r/LocalLLaMA News

Summary

This article reports benchmark results showing that quantization has little effect on knowledge benchmarks (GPQA) but significantly degrades agentic performance (Terminal-Bench 2) for Qwen 3.6 models, with further observations on timeout settings and run variability.

TL;DR: Quantization has a marked impact on agentic performance but little effect on knowledge. I manage a small HPC cluster at a university, and we have recently begun running common benchmarks to help our users understand the effects of quantization. We have just completed the runs on the Qwen 3.6 quantizations and posted the results on our website: https://scrp.econ.cuhk.edu.hk/llm-benchmark The results are consistent with what most people would expect: knowledge, as measured by GPQA Diamond, varies very little across quantizations. GPQA Chart Agentic use, as measured by Terminal‑Bench 2, shows a significant regression in the lower‑precision quantizations. Terminal-Bench 2 Chart We also observed a notable drop compared with Qwen’s official FP8 scores. We believe this stems from the timeout setting—we use Harbor’s default, which ranges from 10 minutes to 1 hour depending on the task, whereas Qwen’s official figures were produced with a flat 3‑hour timeout. On the website you’ll also see the range of scores from multiple runs. There is considerable variation across runs; a poor run with a higher‑precision quant can easily be worse than a good run with a lower‑precision quant. We are currently benchmarking the GLM‑5.2 quantizations, but, as expected, the process is very slow.
Original Article

Similar Articles

Qwen 3.6 35B A3B vs Qwen 3.5 122B A10B

Reddit r/LocalLLaMA

User reports Qwen 3.5 122B significantly outperforms Qwen 3.6 35B on multi-step tasks despite benchmark claims, questioning if quantization or setup issues are to blame.

Qwen 3.8 27b just feels… ok?

Reddit r/LocalLLaMA

A software developer shares a skeptical review of Qwen 3.8 27b running locally on 32GB VRAM via Unsloth's Q6 quantization, arguing that benchmarks and online hype overstate the model's real-world coding ability. They report frequent thinking loops, degraded quality with the Swift 1.5 finetune, and a perceived disconnect between public sentiment and actual model effectiveness.