[GE users] Resource Quota Set to restrict by h_rt

reuti reuti at staff.uni-marburg.de
Mon Mar 1 21:01:09 GMT 2010


Am 01.03.2010 um 16:19 schrieb mhanby:

> Is it possible via RQS to do the following pseudo code:
> limit users {*} to slots=10 where h_rt>36:00:00
> limit users {*} to slots=64

it should work when you define two queues with different h_rt limits  
and so limit the slots each user can use in each queue. This might  
lead of course to the situation, that a short running job can start in  
the queue for longer jobs (unless you request the queue explicitly).

Another approach could be to define two projects, which users have to  
specify for short and long running jobs, then you can stay with one  

In principle two or more limits can be specified:

limit users {*} queues long to slots=10
limit users {*} queues short to slots=54,h_rt=129600

Unless the limit is also requested with -l h_rt=3600 or alike, it  
won't be enforced though. Maybe it would be an RFE to add a new  
condition "where", where "where" is a resource request. Would also  
ease the setup for other resource limits:

limit users {*} resources big_io to jobs=10
limit users {*} to jobs=50

-- Reuti

> In other words, limit each user to 10 slots for jobs requesting 36  
> hours or more of wall clock, and restrict their total slots to 64  
> (so they could potentially have 54 slots that requested < 36 hours  
> along with 10 using > 36 hours.
> Thanks,
> Mike
> =================================
> Mike Hanby
> mhanby at uab.edu
> Information Systems Specialist II
> IT HPCS / Research Computing
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=246536
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net 
> ].


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list