In the examples we provide to researchers we suggest that the point of
using srun within a script submitted with sbatch is that you would append
an ampersand so that you can run multiple job steps in parallel.
The allocations in the #SBATCH directives provide at least the sum of
resources for para
What we say at our site is that you should use srun, if you don’t use srun, you
will see limited, if any, output on resource usage in the various places you
can see it (sacct, etc), and I learned recently that sattach won’t work either.
I find it’s also easier to make mistakes with resource use
Hello Michael,
I don't have an elegant solution, but I'm writing mostly to +1 this. I
didn't catch this in the release notes but am concerned if it is indeed the
new behavior. Researchers use scripts that rely on --cpus-per-task (or -c)
as part of, e.g., SBATCH directives. I suppose you could simp
Hello,
I haven't really seen this discussed anywhere, but maybe I didn't look
in the right places.
After our upgrade from 21.08 to 23.02 we had users complaining about
srun not using the specified --cpus-per-task given in sbatch-directives.
The changelog of 22.05 mentions this change and exp
