[GE users] subordinate queues

llikethat bharanitn at yahoo.com
Wed Nov 24 05:35:29 GMT 2010

    [ The following text is in the "iso-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

--- On Tue, 23/11/10, reuti <reuti at staff.uni-marburg.de> wrote:

From: reuti <reuti at staff.uni-marburg.de>
Subject: Re: [GE users] subordinate queues
To: users at gridengine.sunsource.net
Date: Tuesday, 23 November, 2010, 6:26 PM

Am 23.11.2010 um 13:34 schrieb sgenedharvey:

>> From: llikethat [mailto:bharanitn at yahoo.com</mc/compose?to=bharanitn at yahoo.com>]
>> Can someone please explain the use case of subordinate queues. in which
>> situation it plays a vital role. I read the documentation and it says it can be
>> used for high priority and low priority jobs. The subordinate queue uses the
>> slots as an attribute, how does this help.
> To tell the truth, I've been deploying SGE for around 10 yrs now, and I don't get it either.
> I write wrapper scripts around qsub anyway.  To get all the other arguments that you want standard.

This can nowadays also be achieved by an JSV.

Thank you for the reply. I'm looking at
<http://wikis.sun.com/display/gridengine62u3/Example+-+Writing+a+JSV+Script+Using+the+Bourne+Shell>will get back if i have any doubts.

>  So it's trivial to include job priority in the script.  And when the time comes that all the execution hosts are used, and you need to preempt some job ... Just preempt the number of individual jobs you need.  Why on earth preempt the whole queue?
> In 6.2u5, there's the new feature, 'slotwise preemption' which allows individual jobs of subordinate queues to be preempted.  I just don't get why you would want to set things up this way, instead of preempting jobs by their jobid.  It seems to me, that with slotwise preemption, you can finally come close to the same level of functionality.

I think this must be seen from the history: one big SMP machine with 128 cores. You want to suspend all jobs in the low priority queue when the high priority queue uses slots from a certain amount onwards. I.e. first you allow some kind of oversubscription, but at one point the low priority queue will be preempt completely. For one or two cores, there is no feasable range of values to chose from to start the preemption. But with 128 cores, you could say to allow 64 in the high priority queue and if it's getting more, the low priority queue will be preempt. This could also be seen in combination with a functional policy, where the high priority jobs won't get niced (i.e. reprioritized by the scheduler), but the low priority ones (as long as they are running).

-- Reuti


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net</mc/compose?to=users-unsubscribe at gridengine.sunsource.net>].

More information about the gridengine-users mailing list