Technical Report No. 12

Qwen3.8-Max across the effort knob

2026-08-04 · 23 tasks · 202 runs · 3 effort levels · v3 suite · $126.25
Abstract.

The effort knob runs backwards, further than any model measured here: 81.2% at low, 71.0% at medium, 55.1% at xhigh. That is a 26-point fall to the lowest column on the v3 board, and because xhigh is the API default, an untuned integration gets the worst setting. The deficit is unfinished work, not bad work: wrong answers vanish (3 → 0 → 0) while runs that never finish climb from 14% to 41%. The three tasks it cannot solve fail at every setting; six that low solves 3-for-3 account for 83% of the drop. At $126.25 against DeepSeek V4-Flash’s $13.60 on the same suite, and 19.6–25.5 minutes per task, it is the most expensive and slowest model on the board.

Model card: Qwen3.8-Max scores 81.2% at low effort, 71.0% at medium and 55.1% at its default xhigh setting; unfinished runs climb from 14% to 41% across the same range
Card. Shades darken low → medium → xhigh. Accuracy falls as unfinished runs climb; both panels are zero-based.

Accuracy falls at every step up the knob, and the default is the bottom.

Effortpass@1SolvedWrongUnfinishedCostTokens/taskTime/task$/solved
low81.2%56/69310$42.09188 K19.6 min$0.75
medium71.0%49/69020$38.81157 K21.7 min$0.79
xhigh (default)55.1%38/64026$45.35208 K25.5 min$1.19

pass@1 is the mean per-task success rate across attempts, so uneven attempt counts do not bias it. Wrong = a finished run that failed the hidden tests; unfinished = cut off at the wall-clock or step budget. The xhigh column has 64 runs rather than 69 because five died on 600-second provider-side API read timeouts and are excluded rather than scored zero. Qwen’s documented effort enum is low/medium/xhigh — there is no high — and xhigh is what the API uses when the field is unset.

1.

The knob runs backwards, and steeply. Low leads xhigh by 26 points, more than triple the 9-point inversion Report No. 10 recorded for Claude Opus 5, and far outside the noise: standard errors are ±7.8, ±9.4 and ±9.7 points, and low-vs-xhigh does not overlap.

2.

Effort converts wrong answers into unfinished runs. Wrong answers fall to zero (3 → 0 → 0) while runs that hit a budget climb (10 → 20 → 26). At medium and xhigh every single failure is an incomplete run. Failed runs burn roughly five times the completion tokens of successful ones and three times the clock — work cut off mid-flight, not sloppy attempts.

3.

The regression sits in solvable work. Three tasks score zero at every setting and extra reasoning rescues none of them. Of the nine that regress from low to xhigh, the six that low solves 3-for-3 account for 83% of the drop, three collapsing to zero. It is not losing the hard problems; it is losing the ones it already knows how to do.

4.

Most expensive, slowest, and beaten on every axis. The sweep cost $126.25 against $13.60 for DeepSeek V4-Flash on the identical suite. Every DeepSeek column (88.4 / 87.3 / 85.5) outscores every Qwen column (81.2 / 71.0 / 55.1) with no overlap, at $0.08 per solved task against $0.75–1.19. At 19.6–25.5 min/task it is the slowest model measured on v3, ahead of Kimi K3 at 17.2.

5.

A second clock, imposed by the provider. Five xhigh runs on the suite’s heaviest repositories failed with 600-second read timeouts from the DashScope endpoint — a single request exceeding ten minutes, well inside the harness’s own 45- and 60-minute budgets. No previous report has recorded this. At its default effort, the model can exceed its own provider’s response window.

The nine tasks that moved; the other fourteen scored identically at every setting.

Tasklowmediumxhigh
jiff-strftime-negpad3/33/30/3
semver-inc-dotted-prerelease3/30/30/3
sqlglot-qualify-lateral-star3/31/30/3
packaging-range-prerelease-policy3/33/31/3
semver-xrange-order3/33/31/3
zod-invert-codec3/33/31/3
itertools-strip-prefix3/33/32/3
flask-teardown-robust1/30/30/3
networkx-leiden-communities1/30/30/1

Cells are solved/attempted. Never solved at any setting: aiohttp-upgrade-deferred, pennylane-trotter-fragmented, sqlglot-canonicalize-internal-names. Of the 56 unfinished runs across the sweep, 38 died at the 45-minute (large) or 60-minute (xlarge) wall-clock boundary and only three hit the step ceiling; none was cost-capped. The clock, not the step budget, is what binds.

VulcanBench v3: 23 tasks from real merged post-cutoff PRs (Python 9, TypeScript 4, Rust 4, Go 3, JavaScript 3), network-isolated Docker sandboxes, deterministic hidden-test grading, three attempts per task per configuration. Budgets scale with repository size — 50–200 steps and 5–60 minutes — identical for every model on the board and unchanged since Report No. 07. Qwen3.8-Max priced at $2/$6 per million tokens on the international (Singapore) endpoint. Caveats: with an unlimited budget xhigh might close some of the gap, so this measures capability under a fixed budget rather than a capability ceiling; Qwen also exposes a thinking_budget cap that was not tested, because its API rejects that parameter alongside reasoning_effort, and it is the knob most likely to address the pattern documented here. Unlike Reports No. 07, 08 and 10, every column in this report is three attempts per task; the single-attempt columns those reports established carry wider uncertainty by comparison.

← All benchmarks