golang seems to think 4gb is a 'huge buffer' #21
Merged
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
|
cc @paperstreet |
ioutil.ReadFile won't pre-alloc a buffer of size > 1gb (excepted from ioutil.go):
// Don't preallocate a huge buffer, just in case.
if size := fi.Size(); size < 1e9 {
(from https://golang.org/src/io/ioutil/ioutil.go?s=1464:1510#L60 )
Thus reading a 4gb hfile results in 8gb alloc'ed while growing the buffer.
theevocater
added a commit
that referenced
this pull request
Oct 21, 2015
golang seems to think 4gb is a 'huge buffer'
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.
ioutil.ReadFile won't pre-alloc a buffer of size > 1gb (excepted from ioutil.go):
(from https://golang.org/src/io/ioutil/ioutil.go?s=1464:1510#L60 )
Thus reading a 4gb hfile results in 8gb alloc'ed while growing the buffer.