Number of Cpu's does not work on slurm
See original GitHub issueTrying to use this in a slurm cluster, I always get 1 processor allocated no matter what i put in the req_nprocs
configuration setting.
It seems that the corresponding option is not included in the slurm script template. I tried to edit it, to no avail.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
HPC cluster: select the number of CPUs and threads in ...
In other words, a task cannot be split across multiple nodes. Therefore, using --cpus-per-task will ensure it gets allocated to the same node, ......
Read more >CPU Management User and Administrator Guide
2 jobs each require 6 CPUs (6 tasks per job with no overcommitment). Run both jobs simultaneously in a single node. slurm.conf options:...
Read more >nodes vs tasks vs cpus vs cores - SCG
A communication bus between a Socket/CPU and I/O controllers (disks, networking, graphics,...) in the server. Slurm complicates this, however, by using the terms ......
Read more >How do I control threads and CPUs on Ookami using Slurm?
No. of tasks (e.g., commands to run in parallel) to be run. --ntasks-per-node. No. of tasks to use per node. Often, this will...
Read more >Slurm F.A.Q — CÉCI - CECI
Slurm ignores the concept of parallel environment as such. Slurm simply requires that the number of nodes, or number of cores be specified....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since I don’t have access to every possible batch system, the choices made in the default batch script templates generally reflect the needs of whomever contributed the script for that job manager. If there’s a reason for omitting req_nprocs in the Slurm script, I don’t know what it was.
To the larger point, one of the TODOs after we finalize this release is to revisit the templating system, since the inability to selectively include lines is a clear weakness of the current scheme.
On Wed, Apr 18, 2018 at 9:12 AM, Richard Darst notifications@github.com wrote:
– Michael Milligan, Ph.D. | Supercomputing Institute Assistant Director for | University of Minnesota Application Development | milligan@umn.edu www.msi.umn.edu/staff/milligan | Phone: 612-624-8857
This is fixed now and can be closed.
Please report if something is not correct:
https://github.com/jupyterhub/batchspawner/blob/c0da1f38a52a3c6acc27bd0d93d40b943577097a/batchspawner/batchspawner.py#L525