osd: disable filestore_xfs_extsize by default #7265
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
This option involves a tradeoff: When disabled, fragmentation is worse, but large sequential writes are faster. When enabled, large sequential writes are slower, but fragmentation is reduced. Fixes: #14397
liewegas
added a commit
that referenced
this pull request
Jan 18, 2016
osd: disable filestore_xfs_extsize by default Reviewed-by: Sage Weil <sage@redhat.com>
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.
This option involves a tradeoff: When disabled, fragmentation is worse, but large sequential writes are faster. When enabled, large sequential writes are slower, but fragmentation is reduced.
The reason for setting it off by default is to make performance comparable to that in Firefly and not introduce a perceived large sequential write perf regression.
Fixes: #14397 http://tracker.ceph.com/issues/14397
CC @markhpc @liewegas @idryomov