Backpressure for reading records #438
Merged
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.
Previously driver would read records from network even if client did not consume them. This happened because event loop threads were always in auto-read mode despite the amount of currently buffered records. This could lead to memory problems when handling large results that are slowly consumed.
This PR adds simple network-level backpressure for reading records. Auto-read mode is turned off when amount of buffered records reaches high watermark. It is turned on again when bunch of records are consumed and buffer size reaches low watermark. Also added unit tests for PULL_ALL and RUN handlers.