Track change stream stats independently of generation #145
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
ajayvijayakumar123
approved these changes
Oct 30, 2025
Collaborator
ajayvijayakumar123
left a comment
ajayvijayakumar123
left a comment
There was a problem hiding this comment.
LGTM % a test suggestion!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently we compute change stream speed by looking at the number of events received in the current generation. This can produce inaccurate results when generations are short.
This changeset switches that rate computation to be tracked independently of the generation.
Logging and documentation are also revised to be more helpful regarding change stream lag.