Am 21.02.2011 um 17:00 schrieb Chris Jewell: > Hi all, > > This is a more general question, really, but what is the best way to assign a > default h_rt resource request to jobs? > > I want to be able to set h_rt request default to INFINITY in order to get the > scheduler to segregate "long" jobs from "short" jobs. My short.q will have a > fixed attribute of 30 minutes (and I want it to be accessible only by jobs > which are requested to be < 30mins), while the long.q will have a fixed > attribute of infinity and will be available to all jobs. That way, I can > keep back two execution nodes for my short queue to improve availability. > > At the moment, I have: > > 1. an enforced requestable (fixed attribute, not consumable) for h_rt in the > complex, > 2. h_rt given 30mins in the complex section of the queue config, > 3. A limit of 30mins configured for Wall Time in the same queue, > 3. -l h_rt=INFINITY in sge_request file.
Yes. It's sufficient to have it as limit in the queue though. There is no need to set it also as complex value. Short jobs may end up in the long queue, but usually it's not a problem. When the default is infinity in the long queue, another option could be to have a forced boolean request attached to the short queue. Then you would be of course limited to run short jobs only on the short queue by requesting this complex during job submission. Or you could setup a default queue in a similar way ot request the long queue and it would be possible to override it with a request for the short one at submission time. Use the implementation which suits best to you. -- Reuti > Is that the best way? > > Thanks, > > Chris > > > -- > Dr Chris Jewell > Department of Statistics > University of Warwick > Coventry > CV4 7AL > UK > Tel: +44 (0)24 7615 0778 > > > > > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
