The help for --cwl-min-ram doesn't really explain why you need it (which is to make sure that your Slurm job fits your CWL job that needs 256 MiB of memory and Toil itself which needs more).
We should just add Toils' own idea of its overhead to resource requests in the backing scheduler when scheduling CWL (and WDL) jobs (or at least tiny ones). Then we wouldn't be able to have this problem.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1844
The help for
--cwl-min-ramdoesn't really explain why you need it (which is to make sure that your Slurm job fits your CWL job that needs 256 MiB of memory and Toil itself which needs more).We should just add Toils' own idea of its overhead to resource requests in the backing scheduler when scheduling CWL (and WDL) jobs (or at least tiny ones). Then we wouldn't be able to have this problem.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1844