Hi,

Am 28.03.2012 um 07:53 schrieb Schmidt U.:

> In our clusters I am using rqs like this:
> {
>   name         slot_per_us
>   description  slots fuer user
>   enabled      TRUE
>   limit        users {*} queues !cleaner.q to slots=700
> }
> By now, the slots were adjusted manually from time to time.
> This procedure is not flexible and needs permanent admin control.
> Without these rqs a user could occupy  and block the whole cluster for a long 
> time.
> On the other hand, in rare case of a more or less empty cluster a user should 
> have the possibility to submit and run thousands of jobs for a short time, 
> say 24 hours.

well, SGE has no crystal ball builtin about what will be submitted in the 
future. We face the same problem from time to time. You have the extremes of 
leaving slots unsed in the cluster or allowing a user to fill it completly in 
the morning hours.

Also a share tree policy won't help, if the cluster is empty at certain times. 
It would be necessary to have a share tree policy which blocking the user 
completely if he is well above the granted limit for the last 30 days or so. As 
you pointed out, this might lead to empty slots again.


> So I am thinking about a solution to check all the submit scripts (by jsv 
> script)  and create product of compulsory  h_rt and $NSLOTS. The result 
> should be compared, anyhow, with available slots in the queue to set rqs slot 
> limit individually per user.

Yes, you could compute a value out of h_rt and $NSLOTS and request it as an 
integer value from a defined complex. This complex you can limit again in an 
RQS. So the user can submit a few long running jobs or a bunch of short running 
ones (this complex must also be defined on a global level than with an 
arbitrary value).

-- Reuti


> Is there someone who solved such wishes of the users, maybe in a different 
> way ?
> 
> Udo
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users


_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to