This from Simon, and what Skylar said, are what you should heed.
> In the end our solution was to have strict hard limits (h_vmem) on memory > and to define h_vmem as a consumable complex. To make life easier for our > users though we used a job submission verifier to add a default allocation > of 1GB to any job which didn't ask for any memory. This covers all of the > small jobs. For larger jobs we simply tell people to ask for more than > they need if they're only doing something once, or if they have a bunch of > jobs to run then run one with too much memory allocated and then use qacct > to look at the actual max usage so they know what they should ask for next > time. We had some teething troubles with this for a few weeks after it was > introduced, but it's all been working smoothly for a long time now. > > -- Ian Kaufman Research Systems Administrator UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
