Point out sparse file writes in common issues #434
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
The issue of slow header writes pop up quite often, and it's likely that the culprit is actually a slow file system for sparse writes. It is certainly useful to point this out in the common issues section in the readme, as well as briefly mention sparse writes in the docs for create.
jokva
force-pushed
the
common-issues-slow-header-assign
branch
from
b111e3b to
86f24fc
Compare
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.
The issue of slow header writes pop up quite often, and it's likely that
the culprit is actually a slow file system for sparse writes. It is
certainly useful to point this out in the common issues section in the
readme, as well as briefly mention sparse writes in the docs for create.