perf: optimize weekly digest aggregation - #30
Merged
Conversation
sarthakagrawal927
marked this pull request as ready for review
August 10, 2026 07:04
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.
What
Why
CodeVetter repeatedly selected weekly digest generation as an application hotspot. The source experiment moved from a 16.181 ms/op observed baseline to 7.266 and 7.534 ms/op on later runs.
Evidence boundary
This is directional evidence, not a paired-confirmed percentage claim: the original baseline capsule was not retained for the identical paired verifier. The draft should merge only after normal repository review.
Checks