-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/02/14 10:46, Bill Wichser wrote:
> In the case presented, again I'll say, it is clearly evident that > the job waiting, number 300, can run. It has free cores, the job > currently waiting will have plenty of cores available when the job > it is waiting on finishes, yet it does not start simply because the > time it requires would interfere with the current start time of the > currently waiting job, #201. > > But the assertion that job 201 would be held up by starting job 300 > is completely incorrect in this case. So if I'm interpreting you correctly you are saying that Slurm is not taking into account the fact that cores that will be released from jobs finishing. I wonder if that's because it's not a guarantee as the job may get extended by an administrator, or on a multi-node system the node itself may fail? All the best, Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] 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/ iEYEARECAAYFAlMGukMACgkQO2KABBYQAh9nRACfY0aaO3Mb9L2jsY/s8AfDb/qw XecAn1gzN9NXuilyIHqaUx3po2AQukQM =F+bb -----END PGP SIGNATURE-----
