perf: ensure full write buffer for *File.ReadFrom #623
Conversation
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
In `*File.ReadFrom`, ensure that the buffer is filled to capacity (`maxPacket` length) before performing the write. Prior to this change, the amount of data read into the buffer was dictated by the `io.Reader`'s `Read` implementation, and write performance would suffer when the Read would return less than maxPacket bytes of data. An example source would be a `net/http` response `Body` from a TLS server, which seems to cap each read to 16384 bytes -- half the default max packet size of 32768 bytes.
puellanivis
approved these changes
Mar 24, 2025
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.
In
*File.ReadFrom, ensure that the buffer is filled to capacity (maxPacketlength) before performing the write.Prior to this change, the amount of data read into the buffer was dictated by the
io.Reader'sReadimplementation, and write performance would suffer when the Read would return less than maxPacket bytes of data. An example source would be anet/httpresponseBodyfrom a TLS server, which seems to cap each read to 16384 bytes -- half the default max packet size of 32768 bytes.