Closed priyanka-surana closed 1 year ago
nf-core lint
overall result: Passed :white_check_mark: :warning:Posted for pipeline commit ebf0747
+| ✅ 132 tests passed |+
#| ❔ 20 tests were ignored |#
!| ❗ 1 tests had warnings |!
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.
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.
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.
Does COOLER need 200gb anyway? We get away with 100 for almost everything and even that is too large as a starting point.
Honestly, we have not started analysing our log data. Currently it is assigning, 72GB (label: high) but I can reduce it further.
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).