Increase ram #101
Merged
Increase ram #101
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
|
I played a bit around here. When you have two mammalian genomes (such as human and seal) than the RAM gets really crazy... e.g. for BBDUK. I would leave the PR and setup now like it is. At least that should increase the changes of getting the pipeline done w/ some retry and RAM increases but might not work for all large inputs. |
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.
I experienced this problem before and just confirmed it while doing new analysis for MARRES. At least on the HPC, process might fail due to out of RAM and then error code 1 is thrown.
With this change, I catch it and resume with more RAM.
Disadvantage: when the process fails w/ error code 1 due to another problem, it will resume a few times but then still fail.