Set the default number of threads to the number of CPUs/cores the process is really allowed to use #620
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
Some of our users execute OrthoFinder on our Linux HPC cluster which runs under Slum Scheduler. Here is the problem: even if the user sets -c/--cpus-per-task option correctly, OrthoFinder doesn't take it into account. The default "parallel sequence search threads" remains the total number of cores of the compute node OrthoFinder is running on instead of the number of cores the OrthoFinder process can really use on that node (set by the Slurm option in our case and enforced by cgroup).
OrthoFinder can't take that enforcement into account because nThreadsDefault is computed using os.cpu_count() in scripts_of/util.py rather than len(os.sched_getaffinity(0)).
Would you consider changing the way nThreadsDefault is set? I know sched_getaffinity doesn't exist in Python 2.7 but maybe you are planning to drop the python 2.7 support in a future release?
Thanks in advance,