Repository navigation
Improved backpressure algorithm - #3
Merged
Merged
Conversation
Turns out that the algorithm that I wrote for client selection was highly inefficient, because it constantly made clients to create new connections. This new algorithm uses a LIFO queue to select the latest client that drained, and keep using it until it is full.
1 task
1 task
1 task
1 task
1 task
This was referenced May 28, 2025
1 task
1 task
1 task
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
1 participant
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.
Turns out that the algorithm that I wrote for client selection was
highly inefficient, because it constantly made clients to create
new connections. This new algorithm uses a LIFO queue to select
the latest client that drained, and keep using it until it is full.