docs: record keep-or-revert bench process - #3
Merged
Conversation
Capture local vs remote Boost bench rules, how to read GCC noise, and that issues and PRs are English. Co-authored-by: Cursor <cursoragent@cursor.com>
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
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.
Summary
docs/BENCH.md: keep-or-revert, local vs remoterelease-bench, and how to read GCC/Clang noise (try_push/fulltimer floor, Boost 4096/4097 bimodal,copy/fullalloc).This was the second commit on #2. The squash merge of #2 only landed the hoist; this restores the docs.
Test plan
docs/BENCH.mdagainst./scripts/dev.sh bench/fetch-ci-bench/compare-benchdocs/BENCH.mdMade with Cursor