-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update maxRetries #86
Conversation
|
What's the likely hood that process_high_memory processes will need 5 retries? If it does go through and ends up trying to request 1tb of mem, that will cause issues won't it? Especially as the sanger.profile caps out at 680. Does COOLER need 200gb anyway? We get away with 100 for almost everything and even that is too large as a starting point. |
This feature is generally only used by fastK and sort. Jobs that exceed the max.mem in sanger.config will get capped. And if they fail with max.mem, you are right they will get repeated with similar resources.
Honestly, we have not started analysing our log data. Currently it is assigning, 72GB (label: high) but I can reduce it further. |
Trying it out directly in GitHub 😱
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Increasing the maxRetries wrt changes in the
sanger.config
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).