fix: use unbounded channel for worker write queue#157
Open
ltungv wants to merge 1 commit into
Open
Conversation
worker write channel size grows with the process rate of the apply thread. flushes are also assumed to be relatively cheap. keeping `read_rx` bounded also prevent the system from being flooded by external requests.
|
wow, massive PR |
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.
prevent deadlock by making one of the channels unbounded so that send never blocks on the apply thread.
worker's write channel size grows with the process rate of the apply thread. flushes are also assumed to be relatively cheap. keeping
read_rxbounded also prevents the system from being flooded by external requests.closes #153
local checks