[torqueusers] getting torque to enforce memory limit (resources_available.mem)

Gareth.Williams at csiro.au Gareth.Williams at csiro.au
Fri Oct 11 05:24:08 MDT 2013


Hi Sam,

We schedule memory based on vmem and it works adequately (torque+moab but maui is probably OK too).
I can provide more detail if necessary.

Regards,

Gareth

From: Sam West [mailto:swest at sgi.com]
Sent: Thursday, 10 October 2013 3:44 AM
To: Torque Users Mailing List
Subject: [torqueusers] getting torque to enforce memory limit (resources_available.mem)

All our efforts to get torque+maui to schedule and run jobs, while respecting a node's maximum available memory are not working...

This seems like one of the most basic functions that a queuing system should be able to perform, so I assume we are just doing something wrong.

We want users to be able to qsub jobs, with memory limits specified, and to have torque/maui keep track of the aggregate memory requested by various jobs, and not place jobs into execution if the aggregate memory exceeds the available.

We believe we are currently configured to make this happen (i.e., we have our batch queue resources_available.mem set to the maximum that we want to be allowed).  Can someone point to an example of a queue configuration that correctly implements this feature?

Thanks.

- s.west
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torqueusers/attachments/20131011/292ba3bd/attachment.html 


More information about the torqueusers mailing list