-
Notifications
You must be signed in to change notification settings - Fork 2
Add adaptive message batching to reduce overhead under load #821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 16 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
6118fee
Add adaptive message batching to reduce overhead under load
SimonHeybrock 92b938c
Replace count-based adaptive batching with processing-time-aware MIAD…
SimonHeybrock 9c0e80b
Initial adaptive batching scenario tests
SimonHeybrock a2b9232
Add batch time reporting
SimonHeybrock 5784752
Strengthen adaptive batching scenario tests
SimonHeybrock 50d3589
Add failing tests for de-escalation under continuous load
SimonHeybrock b8735dc
Fix de-escalation under continuous load
SimonHeybrock bd58a0b
Add tests for de-escalation dead zone, sticky jitter, and time gaps
SimonHeybrock 218eeeb
Add cosmic background to shutter tests, test severe-to-cosmic path
SimonHeybrock 92b5d17
Replace 2x de-escalation with sqrt(2) half-steps
SimonHeybrock b7e9714
Inline
SimonHeybrock 4badafa
Fix message loss during adaptive batch level transitions
SimonHeybrock 014e067
Improve adaptive batching scenario tests
SimonHeybrock 17726e6
Tune adaptive batching scenario test limits and strengthen GC jitter …
SimonHeybrock 0db01a9
Consolidate adaptive batching scenario tests
SimonHeybrock 2c74c83
Trim simulation durations to reduce steady-state tails
SimonHeybrock a7311c3
Merge branch 'main' into adaptive-batching
SimonHeybrock File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this a warning? Do you consider a batch change to be a config error? It seems to me like these changes will be common and part of normal operation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not consider it a config error in general. I expect in many cases that the batch size can be the minimum (1 second), but for larger or un-optimized data-reduction I expect that the batch size needs to be improved.
I think the scenarios may give a wrong impression - I hope that we can stay at the minimum batch size almost always. Batch size increases are there to deal with spikes in the backlog (such as GC running), or as a way to keep operating without dropping data, until we have scaled our system (e.g., by running more backend workers).