Repository navigation
perf(detection): charge the scan budget per pass and cut monitor overhead - #113
Merged
Merged
Conversation
…attern The per-request scan time budget read the thread CPU clock around every pattern. It now charges per pass: one read when a pass opens, one at each 2 ms wall-clock slice boundary and one when the pass closes. The per-pattern check reads only a cheap monotonic clock and compares the charged total, so the budget lags the true spend by at most one slice plus one pattern.
github-actions
Bot
added
area: engine
This was referenced Oct 16, 2026
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.
Closes #112
Port of the reference fix in Guard-Core/guard-core#173. timeExhausted now reads only the monotonic clock per pattern and charges the CPU clock at 2 ms slice boundaries (the slice lives on the request budget, so it spans passes), with the final charge when the pass closes, so the budget lag is at most one slice plus one pattern. The performance monitor skips the sanitized anomaly copy when no callback is registered. Tests cover the clock reads per pass and a long pass stopping within one slice of the budget; coverage stays covered-or-waived 100% with no new waivers. On a ~1 KB JSON-like value plus 10 short header values detection went from 5.60 ms to 5.43 ms of CPU.