Avoid unnecessary IoTConsensus batch accumulation delay - #18522
Open
Caideyipi wants to merge 1 commit into
Open
Conversation
jt2594838
approved these changes
Aug 25, 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
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.
What is changed?
The accumulation/config-reload changes from #18501 are preserved, but the dispatcher no longer sleeps for the full accumulation interval after a batch has already filled. It now waits on the pending-entry queue with a deadline and stops immediately when the configured entry limit is reached.
This removes the sustained-write throughput regression in IoTConsensus; IoTv2 does not use this dispatcher path. A regression test covers the full-batch case.
How Has This Been Tested?