[GE users] Defining priority of hosts

Bisbal, Prentice PBisbal at LexPharma.com
Wed Aug 30 16:44:41 BST 2006


I read the information on the page below. It mentions creating different
queues for each class of system, and assigning different sequence
numbers to each queue. Is it possible to just assing a different
sequence number to each host's queue instance instead? 

-----Original Message-----
From: Chris Dagdigian [mailto:dag at sonsorol.org] 
Sent: Tuesday, August 29, 2006 7:03 PM
To: users at gridengine.sunsource.net
Subject: Re: [GE users] Defining priority of hosts


One method to do  this would be to switch from load based sorting to one
based on sequence numbers. You can then number hosts with a sequence
number that reflects relative speed.

This may be a good start:
http://blogs.sun.com/sgrell/entry/n1ge_6_scheduler_hacks_sorting

-Chris



On Aug 29, 2006, at 5:09 PM, Bisbal, Prentice wrote:

> Greetings, everyone.
>
> I'm a GridEngine newbie, so please forgive me if this is a simple/ 
> dumb question. I searched through the docs, and couldn't find an 
> answer there. I could have been using the wrong terminology in my 
> searches.
>
> I'm not sure if "priority" is the correct term in GridEngine parlance.

> Here's what I'm trying to do: My execution hosts are a mixture of 
> different systems, from old SGIs to new multi-core, multi-processor 
> Opterons. All systems are in the same queue. When jobs are submitted, 
> I'd like them to be assigned to the fasted idle computer available, 
> instead of randomly assigned or round-robbined.
>
> For example, if host A has 4 processors. Host B has 8 processors, but 
> those processors are only 1/2 as fast as host A. If I submit 5 jobs, I

> want all 4 processors of  host A filled before jobs are assigned to 
> host B.
>
> What is the best way to do this?
>
>
> Prentice
>
>
>
> The contents of this communication, including any attachments, may be 
> confidential, privileged or otherwise protected from disclosure.
> They are intended solely for the use of the individual or entity to 
> whom they are addressed. If you are not the intended recipient, please

> do not read, copy, use or disclose the contents of this communication.

> Please notify the sender immediately and delete the communication in 
> its entirety.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net





The contents of this communication, including any attachments, may be confidential, privileged or otherwise protected from disclosure.  They are intended solely for the use of the individual or entity to whom they are addressed.  If you are not the intended recipient, please do not read, copy, use or disclose the contents of this communication.  Please notify the sender immediately and delete the communication in its entirety.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list