Recommend a stripe count of 32 for large files #300
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recommend 32 instead of unlimited (-1; in practice ~160 on capstor, i.e. the number of OSTs) for large files.
Thanks to @mpasserini for the recommendation. This also the default stripe count amazon uses (https://docs.aws.amazon.com/fsx/latest/LustreGuide/performance.html#striping-pfl). NERSC recommend against using too many OSTs as well, but just say not to use more than 128 (https://docs.nersc.gov/performance/io/lustre/). NASA doesn't explicitly recommend a number, but uses 32 in their example (https://www.nas.nasa.gov/hecc/support/kb/lustre-progressive-file-layout-(pfl)-with-ssd-and-hdd-pools_680.html).