Avoid copying the whole file into RAM to detect its content type #214
Conversation
This file contains 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
request.buildHTTP copies the whole files into RAM to detect their content types, but it increases RAM usage if there is a large file. Since http.DetectContentType only considers at most the first 512 bytes of data, we can avoid copying the whole data. Signed-off-by: Junpei Kawamoto <kawamoto.junpei@gmail.com>
|
LGTM. |
youyuanwu
approved these changes
Sep 5, 2021
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.
request.buildHTTPcopies the whole files into RAM to detect their content types, but it increases RAM usage if there is a large file. Sincehttp.DetectContentTypeonly considers at most the first 512 bytes of data, we can avoid copying the whole data.This PR fixes #213.