Add the 1620th column to the performance table (#167) - #795
Merged
Conversation
The first new column since the 1446th, because the Kernel Benchmark filtered on a path that does not exist and had not run since 2026-01-02 -- ninety-eight merged pull requests went unmeasured. The numbers come from the first run after that filter was fixed, on master at e05d717. #167 asks for two things. The commit numbers are already links, and the file already documents how to count one -- that half is done. This is the other half. What the column shows, against the 1446th: ParseHard 5,657,058 -> 2,617,362 ns SimplifyHard 4,880,264,786 -> 2,848,037,261 ns SolveEasy 45,587,157 -> 21,829,186 ns SolveMediumHard 453,280,166 -> 124,316,631 ns SolveHard 3,494,150,836 -> 1,134,532,585 ns CompileEasy 589,540 -> 352,800 ns A note is added above the table saying that columns are not measured on one machine -- this one is a GitHub-hosted runner, the earlier ones are contributors' own machines -- so a row is a trend and not a ratio, and a few per cent between neighbours means nothing. Without that the reader has no way to know, and the moves above are large enough to survive the caveat anyway. What #167 still wants and this does not give is a column for the cost of arbitrary-precision trigonometry, which needs a benchmark that does not exist yet rather than a measurement of one that does. Co-Authored-By: Claude Opus 5 (1M context) <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.
Addresses #167.
#167 asks for two things. The commit numbers are already links — and the file already documents how to count one (
git rev-list --count <commit>), so that half is done. This is the other half: a new column.The first new column since the 1446th
Not for want of interest — the Kernel Benchmark filtered on a path that does not exist and had not run since 2026-01-02, so ninety-eight merged pull requests went unmeasured (#775, fixed in #789). These numbers come from the first run after that filter was repaired, on
masterate05d7179, the 1620th commit.What the column shows against the 1446th:
ParseHardSimplifyHardSolveEasySolveMediumHardSolveHardCompileEasyA caveat added above the table
Columns are not measured on one machine — this one is a GitHub-hosted
ubuntu-latestrunner, the earlier ones are contributors' own machines. So a row reads as a trend, not a ratio, and a few per cent between neighbours means nothing.Without that note the reader has no way to know. The moves above are large enough to survive the caveat, but they should not be quoted as exact speedups.
What this does not do
#167 also wants a column for the cost of arbitrary-precision trigonometry. That needs a benchmark that does not exist yet, rather than a measurement of one that does, so it is left open — the issue should stay open for it, or that half be split out.
🤖 Generated with Claude Code