docs(benchmark): final 89-task figures for the merged-system arm - #60
Merged
Conversation
The run completed after the section was first published. The complete result is materially stronger and one framing claim needed correcting. cgfinal is the FIRST arm to beat baseline on the raw 89-task total -- $94.95 against $100.81 -- and solves the most, 65 of 89. No arm in the original four-way study managed either. That matters because the raw total is the harder bar: six degenerate baseline trials flatter the baseline column, which is why the correction box exists. Both reference arms reproduce their published totals exactly (baseline $100.81, cg-old $102.55), which is the check that the harness and cost model are unchanged across the two studies. Clean-set figures updated to the final 82-task set: 62 solved vs 54, steps 2,865 vs 3,117, $83.52 vs $98.70. The aggregate is -15.4% rather than the interim -16.4%, and path-tracing alone still carries about half of it (-8.3% without it), so the median per-task figure of -7.7% remains the one to quote. Adds two limitations that only the completed run revealed: caffe-cifar-10 is unscored (reward=None at 2,361 s of a 4,800 s budget), so it is in the clean set for cost and out for the solve count -- baseline also failed it; and five arm exceptions are genuine 4x wall-clock timeouts, counted as reward-0 as in the original study. mkdocs build --strict passes. Signed-off-by: Osher-Elhadad <Osher.Elhadad@ibm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Terminal-Bench run completed after #59 published its interim section. The complete result is materially stronger, and one framing claim needed correcting downward.
The headline improved
cgfinalis the first arm to beat baseline on the raw 89-task total — $94.95 against $100.81 — and it solves the most, 65 of 89 (73.0%). No arm in the original four-way study managed either.* cited from the original study, not re-derived — their trial artifacts are pruned from disk.
Beating the raw total is the harder bar, which is worth saying explicitly: six degenerate baseline trials flatter the baseline column, and that is exactly why the correction box exists further down the page.
Both reference arms reproduce their published totals exactly (baseline $100.81, cg-old $102.55). That is the check that the harness and cost model are unchanged across the two studies — without it, a 5.8% improvement could just be drift.
One claim corrected downward
The clean-set aggregate is −15.4%, not the interim −16.4%, on the final 82-task set (62 solved vs 54; steps 2,865 vs 3,117; $83.52 vs $98.70).
And
path-tracingalone still carries about half of it — −8.3% without it — so the median per-task figure of −7.7% remains the number to quote for a normal task. That framing is unchanged from #59 and is the point of publishing both.Two limitations only the completed run revealed
caffe-cifar-10is unscored (reward=Noneafter 2,361 s of its 4,800 s budget). It is in the clean set for cost and out of it for the solve count. Baseline also failed it, so the comparison is not skewed by the exclusion — but the asymmetry needs stating rather than quietly resolving one way.Unchanged
Everything else in the section stands: cache-write/cache-read back to 1.86%, identical to baseline (the previous arm ran 2.86%); #40 explicitly unverified by this arm because its only callers are the three excluded components;
cachesplitstructurally inert on TB's Agent-SDK traffic; and the four published regressions, includingsystem-administrationat +17.2% cost and −2 solved.mkdocs build --strictpasses.