Attention: Want an end-to-end pipelining solution for GATK Best Practices?
Forcing cromwell to submit all possible jobs at once
When I use cromwell to submit jobs on LSF and on AWS (SGE) I often see cromwell submitting only a fraction of the available jobs to submit. So if I have a 1000 jobs often times there's only 100 jobs pending at the same time. Not only does this behavior waste time it also gives problem on AWS, where the # of queueing jobs is used to determine scaling behavior. Is there a way to force Cromwell to submit as many jobs as possible into the job scheduler?