Coalesce empty checkpoints to reduce API calls in high-concurrency map/wait scenarios#336
Open
AdityaAudi wants to merge 1 commit intoaws:mainfrom
Open
Coalesce empty checkpoints to reduce API calls in high-concurrency map/wait scenarios#336AdityaAudi wants to merge 1 commit intoaws:mainfrom
AdityaAudi wants to merge 1 commit intoaws:mainfrom
Conversation
…ts (used by map/parallel branch resubmitters when resuming from timed waits) no longer count toward the 250-operation batch limit beyond the first. This prevents 300+ concurrent branch resumes from splitting across multiple API batches.
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
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.
Summary
Implements the empty-checkpoint coalescing optimization described in #325.
When many concurrent
map/parallelbranches resume from awaitoperation simultaneously, each branch's resubmitter enqueues an empty checkpoint (noOperationUpdate). Previously, these counted toward the 250-operation batch limit, causing 300 concurrent branches to produce 2 API calls (250 + 50) instead of 1.effective_operation_countseparately fromlen(batch)