This repository was archived by the owner on Oct 17, 2026. It is now read-only.
Repository navigation
test(perf): time the fastest batch so load can't fail the gate - #7
Merged
Merged
Conversation
The debug ranking gate averaged twenty runs, so one busy moment on a loaded Mac pushed it over budget: main itself measured 37 and 45 ms against 40 while its fastest runs took 11. Load can only slow a batch down, so the fastest of five batches measures the code rather than the machine. The budget is unchanged.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
The debug ranking gate averaged twenty runs. On this Mac, routinely at load average 20–48, one busy moment pushed it over its 40 ms budget and the pre-push hook refused the push. Interleaved runs on unchanged
mainmeasured 37, 45, 14, 11, and 13 ms.Approach
Time five batches of four runs and keep the fastest. Other work can only slow a batch down, so the fastest batch is the closest measurement of the code itself. The same twenty calls, the same 40 ms budget.
Look at sceptically
Checklist
scripts/task checkpasses locally (three runs at load ~19: 9.2, 9.4, 12.8 ms)