Repository navigation
run: count-based baselines for a deterministic PR check - #20
Merged
Merged
Conversation
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.
--save-baseline f.jsonrecords the median number of each call label per request for every route (from the one-at-a-time probe), plus N+1 / error problems.--baseline f.jsoncompares and exits 1 when a route makes more calls or a new problem appears; fewer calls are reported as improvements.Counts, not timings: on this shared machine the same run varied 2x in throughput, so timing gates would be flaky. Checked on the planted N+1 app: identical runs pass 3/3; a batched baseline vs the N+1 version fails with
… 0 → 12 per request (an N+1?). Blocking findings are deliberately excluded (timing-based).