[WIP] Add checkpoint stress benchmarks and CI gates#630
Draft
[WIP] Add checkpoint stress benchmarks and CI gates#630
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
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\n- add a new brutal checkpoint benchmark harness with absolute p99 gates\n- benchmark basic checkpoint scenario (~100 files, <1k lines) with p99 < 100ms target\n- benchmark long-history churn scenario (100 files x 10k lines x 100 checkpoint series) with p99 < 250ms target\n- run the full checkpoint stress gate in PR and nightly performance workflows\n\n## Notes\n- this is intentionally a red-team workload and expected to be punishing\n- local full run currently fails both thresholds on this branch\n\n## Local full-run result snapshot\n- basic_checkpoint p99: 214.885ms (target <100ms)\n- churn_long_history_checkpoint p99: 371.939ms (target <250ms)\n