[Perf Improvement] Random reads should re-use previous reader even if existing reader can serve the request #1683
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.
Description
Random reads were not working as intended; they did not reuse the existing reader, even when existing reader had the data to serve the request.
This issue occurred because we were using the Read method (instead of ReadFull). According to the documentation, this method does not wait for the entire data to be available, preventing the reader's start offset from being moved by the required number of bytes.
Fix: We should use io.ReadFull() instead.
Before this change:
After this change:
Link to the issue in case of a bug fix.
Internal bug b/322770463
Testing details