d in newer deployments of
> Slurm.”
>
>
>
> I am curious about this statement. Would someone expand on this, to either
> support or counter it?
>
>
>
> Jenny Williams
>
> UNC Chapel Hill
>
>
>
>
>
> *From:* Shunran Zhang via slurm-users
> *Sent:*
If you are letting systemd taking most things over, you got systemd-cgtop
that work better than top for your case. There is also systemd-cgls for
non-interactive listing.
Also mind to check if you are using cgroup2? A mount to check your cgroup
would suffice. As cgroup is likely not supposed to be
Assuming all node need to run the same task once...
How about -n num_of_nodes --ntasks-per-node=1 ?
Otherwise if it is more deployment related I would use ansible to do that.
S. Zhang
On 2025/02/19 2:37, John Hearns via slurm-users wrote:
I am running single node tests on a cluster.
I can se
Arnuld,
You may be looking for the srun parameter or configuration option of
"--oversubscribe" for CPU as that is the limiting factor now.
S. Zhang
On 2024/06/21 2:48, Brian Andrus via slurm-users wrote:
Well, if I am reading this right, it makes sense.
Every job will need at least 1 core j
Hi Arnuld,
What I would probably do is to build one for each distro and install
them either directly into /usr/local or using deb package.
The DEBIAN/control is used by apt to manage a couple of things, such as
indexing so apt search shows what this package is for, which package it
could rep
Hi Arnuld
It is most important to keep the Slurm version the same across the board.
As you are mentioning the "deb" package I am assuming all of your nodes are
of a debian-based distribution that should be close enough for each other.
However, Debian based distros are not as "binary compatible" a
