On 31/05/16 18:42, Diego Zuccato wrote: > What I did is the other way around: I've used cpuset to "pin" the job to > the allocated CPUs. [...] > *Way* less need to watch closely the cluster :)
+lots! We use Slurm's cgroup support to do just that, and Torque's cpuset support (which I agitated for) before that. Unless you're only ever allocating whole nodes to jobs then I'd strongly suggest taking that path (and use cgroups to restrict memory to what the job requested too). All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
