optimize channel closing to avoid allocations when flushing pending responses #3553
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.
Problem
Scala's
foreach
is quite difficult for the JIT to optimize. The use of shared abstract implementations in Scala's collections makes call sides become highly polymorphic and simple cases like this one end up requiring allocations and interface dispatches.Solution
Use a
while
sincependingResponses
is a mutable queue and can efficiently dequeue elements.Notes