Hi,
Am 23.10.2013 um 03:50 schrieb Ian Mortimer:
> On 22/10/13 17:39, Reuti wrote:
>
>> Correct - there is no "look ahead" feature in SGE - i.e. after the suspension
>> you would be inside thegranted limit again. The suspension is the result of
> > another job in another queue being started. You can try:
>>
>> limit queues !urgent.q hosts {*} to slots=$num_proc
>>
>> with feasible limits inside the urgent.q. For a short time until the
> > suspension starts you allow an oversubscription (although it might
> > be parts of a second only).
>
> If we do that won't it lead to nodes being oversubscribed through the
> high priority queues?
Yes, for a fraction of a second until the subordinations you set up for the
other queues take effect - this has to be set up anyway. But you have to allow
to start the urgent jobs, so that as a result the subordination will suspend
the jobs in the lower queues.
NB: The suspended jobs will still hold the reserved resources like memory and
stay also in the process tree - just stopped to be continued later.
-- Reuti
> The alternative would be to limit the low priority queue to < $num_proc
> but then there'll be times when the cluster is underutilized with free
> slots and low priority jobs pending.
>
>
> Thanks
> --
> Ian
> [email protected] Ian Mortimer
> Tel: +61 7 3346 8528 Science IT
> University of Queensland
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
