Use the unbounded queue always and track seperate counter - #91
Merged
Stephen Belanger (Qard) merged 2 commits intoAug 4, 2026
Merged
Conversation
Stephen Belanger (Qard)
approved these changes
Aug 4, 2026
Stephen Belanger (Qard)
deleted the
use-lazy-alloc-queue-with-seperate-counter
branch
August 4, 2026 10:55
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.
It turns out that the crossbeam bounded queue pre-allocates the entire buffer upon initialization. When we switched to use the bounded queue, gateway containers started to OOM due to the memory of the pre-allocated buffers.
This PR switches the queue to always use an unbounded channel, and separately track the queue length for rejection/acceptance.
No behavior change is expected, and so the existing tests cover this behavior.