docs(benchmarking): Tighten overview analysis#421
Merged
Conversation
Trim the benchmark overview analysis to focus on reviewer-facing takeaways and simplify the benchmark table labels without changing the result data or sorting behavior. Co-Authored-By: GPT-5 Codex <noreply@anthropic.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
1 participant
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.
Tighten the benchmark overview page so the analysis reads as decision-oriented takeaways instead of forensic run notes.
Benchmark Copy
The analysis sections now keep the key recall, cost, and runtime conclusions while removing detailed trace examples that do not change the reader's takeaway.
Run Matrix
The benchmark run table uses shorter labels and lookup maps for model, runtime, and reasoning names. The result data, filters, and sorting behavior stay the same.