You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At nextflow.config, we can set queueSize in executor scope, the number of tasks the executor will handle in a parallel manner. https://www.nextflow.io/docs/latest/config.html?highlight=queuesize#scope-executor
However, when a task uses multiple threads, I guess it's better to specify the total number of threads used by running tasks, rather than specify the total number of tasks sent to the executor.
This will help prevent piled pending tasks for the executor and reduce some random errors.
So I want an option that allows us to specify the maximum number of threads servers can use.
Might need to assume that cpus is properly specified in profiles scope.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
At nextflow.config, we can set
queueSize
inexecutor
scope, the number of tasks the executor will handle in a parallel manner.https://www.nextflow.io/docs/latest/config.html?highlight=queuesize#scope-executor
However, when a task uses multiple threads, I guess it's better to specify the total number of threads used by running tasks, rather than specify the total number of tasks sent to the executor.
This will help prevent piled pending tasks for the executor and reduce some random errors.
So I want an option that allows us to specify the maximum number of threads servers can use.
Might need to assume that
cpus
is properly specified inprofiles
scope.Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions