-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add option to set default number of jobs/CPUs to use #138
base: develop
Are you sure you want to change the base?
Conversation
README.md
Outdated
@@ -42,6 +42,7 @@ Usage: scanpy-cli [OPTIONS] COMMAND [ARGS]... | |||
Options: | |||
--debug Print debug information | |||
--verbosity INTEGER Set scanpy verbosity | |||
--njobs INTEGER Set scanpy default number of jobs/CPUs, defaults to all available |
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.
I would suggest that you keep the default as it was (1 job), then on updates of older scripts, you don't need to change anything (but you can always set the number of jobs explicitly as pursued). Probably also using all available CPUs by default might lead (when forgetting to set this) to some undesirable behaviour (abuse node beyond resources request, use more memory than requested and then get killed due to OOM, etc).
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.
Thanks, Pablo. Very much appreciate this commnent. Done in a50edfb. We were also planning on setting the number of jobs explicitly where applicable while the pipeline is still using an older version of scanpy-scripts
.
Add a
scanpy-cli
option to set the default number of jobs/CPUs that scanpy uses, for parallel computing.