[GE users] Scheduling issue

templedf dan.templeton at sun.com
Wed May 20 07:11:21 BST 2009

That distribution behavior is controlled by the allocation_rule setting 
of your PE. The behavior you're describing is $round_robin. The behavior 
you want is $fill_up. There is no easy way to get exclusive access to a 
machine before 6.2u3. See here for the pre-6.2u3 not-easy way:


In some degenerate cases, like yours may be, it's possible to simply 
always request a number of slots that's a multiple of the core count, 2 
in your case. That gets the same effect as exclusive host access.


rscoelho wrote:
> Hello everyone,
> I'm kind of new to SGE and lately I've been experiencing some problems with the scheduler (SGE version 6.1u5). To give you some sense of what's going on, here's an example. Let's say I have to submit two MPI parallel jobs, each one requires 32 slots to run. Suppose that there are 50 queues available, each queue resides on a single dual core execution host, and also that, besides me, there is no other user logged on to the system.
> When I submit both jobs, one after another, I notice that instead of using 16 queues to run the first job and 16 more queues to run the second job (so this way, it would be 2 slots per queue), the scheduler "randomly" assign the total 64 slots across the available queues. To put it differently, it seems that the scheduler not always tries to fit the pending jobs in the fewest available queues.
> Why is that? And how can I change that? In addition, given that all queues are comprised of dual core execution hosts, how can I assure that the scheduler will not dispatch slots from different jobs to the same execution host?
> Thanks in advance,
> Rafael
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=197229
> 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