2.x: improve request accounting overhead in retry/repeat #5790
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.
This PR improves the request accounting overhead in the
retry
andrepeat
operators.Previously, every individual
onNext
invocation signaled a an item production, which had a lot of overhead since theSubscriptionArbiter
has to serialize invocations ofsetSubscription
,request
andproduced
. The improved algorithm counts theonNext
calls in a field and callsproduced
once with the total count before subscribing to the upstream again.Other small changes:
RetrySubscriber
(sloppy copy-paste),isCancelled()
check torepeatUntil
subscription loop, which was somehow missing.