Thanks for the good resource! I’ll read it carefully.
1 Like
Yes. The SLURM configuration has nothing to do really with what your code does. Esp. The “tasks” in ntasks-per-node does not mean processes/threads or anything. This really means a task like on a todo list and serves SLURM to know how much resources you want (there is also a ncores-per-task or similar). To understand the interpretation of theses settings you need to read SLURM’s documentation. If you allocate less than a full node, usually you have to assign threads/processes to specific cores manually as SLURM cannot to that automatically for you. Which why usually SLURM allocates nodes exclusively per user. This means you’d only hinder yourself if you chose the settings poorly 
1 Like