[FIX] Memory issues in LS5 #803
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
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.
It seems like the memory issues are caused by LS5's particular setting that maps
/tmpinto RAM. You can consume up to 32GB in/tmpthat are discounted from the overal RAM.FMRIPREP was using
/tmpin the resampling of all BOLD scans into T1 and MNI. For long runs and/or many runs, the 32GB limit was reached in fact reducing the total amount of memory for processes to only 32GB (the total in LS5 is 64GB).In this PR some other optimizations are also done: make sure we always close file handlers and memory annotations have been revised to more sensible values.