Fastqc: FIX memory over-allocation
#6156
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
sguizard
requested review from
drpatelh,
KamilMaliszArdigen,
grst and
FelixKrueger
as code owners
|
Can you please add a comment in the code explaining why it is required. |
|
Sure! |
SPPearce
approved these changes
Aug 22, 2024
|
Thanks Simon! |
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.
Fastqc will allocate to the JVM --memory * --threads RAM .
This results in the job to be killed by scheduler for exceeding the amount of RAM requested.
Dividing the
task.memorybytask.cpusallow to stick to requested amount of RAM.