-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/02/14 09:27, Lyn Gerner wrote:
> You might check out the Weight parameter in the Node section of the > slurm.conf documentation. I believe you could just give the fat nodes > a higher node weight than the thinner nodes, to achieve your goal. We use it to ensure that our Xeon Phi nodes are allocated after nodes that don't have them, and that our 512GB nodes are allocated after the 256GB nodes. Of course the 1 node that has both Xeon Phi AND 512GB is very heavily weighted against. :-) Here's the snippet from our slurm.conf (you can see from the Gres and RealMemory directives which are which): NodeName=barcoo[001-058] NodeAddr=barcoo[001-058] RealMemory=250000 Weight=2 NodeName=barcoo[059-060] NodeAddr=barcoo[059-060] RealMemory=500000 Weight=1000 NodeName=barcoo061 NodeAddr=barcoo061 RealMemory=500000 Gres=mic:2 Weight=100000 NodeName=barcoo[062-070] NodeAddr=barcoo[062-070] RealMemory=250000 Gres=mic:2 Weight=100 cheers, 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLxhZ8ACgkQO2KABBYQAh8wxgCdEYsad3KEHLH7MK+iMo+BL1qr ewcAn3TE4hV/C8MdFlmTbExMq9uKmn51 =14xq -----END PGP SIGNATURE-----
