[GE users] queue priorities?

Charu Chaubal Charu.Chaubal at Sun.COM
Fri Jul 23 14:24:56 BST 2004


Don,

Did you look at the presentation that I linked below?

All I can say is that you should probably just read the documentation  
for Grid Engine, since it gives a fairly comprehensive overview of how  
everything works.

Please go to http://docs.sun.com and search for "Grid Engine"

Regards,
	Charu


On Jul 22, 2004, at 6:52 PM, Don Shesnicky wrote:

> Charu,
> I went back searching for the reply on this one as I was buried in  
> another
> problem. If I installed sge 6.0 and created a queue with qmon call  
> queue1.
> Would that be a Share Tree, Functional or Override type of queue ie.  
> what
> is the default queue if you just create a queue in qmon?
>
> I mean there must be a type to the queue if you just open qmon and do  
> Add
> Queue, name one and then save it?
>
> Don
>
> ________________________________
>
> From: Charu Chaubal [mailto:Charu.Chaubal at Sun.COM]
> Sent: Fri 16/07/2004 1:26 PM
> To: users at gridengine.sunsource.net
> Subject: Re: [GE users] queue priorities?
>
>
>
> Don,
>
> [ All of the following applies only to GE 6 ]
>
> There are 3 high-level polices: Urgency, Ticket, Posix-priority
> -- Within the Ticket policy, there are 3 sub-policies: Share Tree,  
> Functional,
> Override
> -- With the Urgeny policy, there are 3 sub-policies: resource urgency,
> wait-time, deadline
> -- The Posix-priority policy doesn't have any sub-policies.
>
> All policies and sub-policies are governed by weighting factors, and  
> so turning
> the weighting factors to zero lets you turn these policies off.
>
> For more info, please see my Cluster World '04 presentation here:
>
> http://www.clusterworld.com/CWCE2004/Charu_Chaubal_presentation.pdf
>
> Regards,
>         Charu
>
>
> Don Shesnicky wrote:
>>
>>
>>> No, you can change the policies during runtime. You can have multiple
>>
>> policies
>>
>>> turned on at the same time, but there are some settings, which might
>>
>> not make
>>
>>> sence to have them at the same time, such as the Functional and the
>>
>> Share tree.
>>
>>> You can use the weighting parameters to weight the different policies
>>
>> among each other.
>>
>> Stephan,
>> Thanks for the reply again. So there are two policies Functional and
>> Share Tree.
>> I take it that Urgency and Override are two others but they aren't the
>> same notion
>> of an overall policy that Functional and Share are ie. a basic
>> scheduling method.
>>
>> I've installed the source and created a few queues, I've used
>> subordinate queues
>> to shutdown lower priority ones when jobs come in on the higher  
>> priority
>> queues.
>> Is there a name for the basic policy that is where you are working  
>> when
>> you first
>> install ie. Basic Policy or is it already one of Functional or Share
>> Tree?
>> Pardon my ignorance but I you have policies such as Functional and  
>> Share
>> that
>> can be turned on then you would think there is a policy when you first
>> startup
>> up the system and create a queue or two. I guess another way to ask it
>> is, is
>> there a default policy that you are building on when you first  
>> install.
>>
>> Don
>>
>>
>>> Don
>>>
>>> -----Original Message-----
>>> From: Charu Chaubal [mailto:Charu.Chaubal at Sun.COM]
>>> Sent: Friday, July 16, 2004 10:36 AM
>>> To: users at gridengine.sunsource.net
>>> Subject: Re: [GE users] queue priorities?
>>>
>>> What I described is part of Grid Engine 6.  There is only one version
>>> of Grid Engine 6, so I'm not sure what you mean by basic system.....
>>>
>>> If you install GE 6, do 'qconf -ssconf' and you'll see parameters
>>> related to urgency policy and waiting-time.
>>>
>>> regards,
>>>      Charu
>>>
>>> On Jul 16, 2004, at 7:29 AM, Don Shesnicky wrote:
>>>
>>>
>>>
>>>
>>>> Charu,
>>>> Is this in the basic system or in the share based or functional  
>>>> policy
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>> setups? I'm going to try to setup a test case with one or the other
>>>> today.
>>>>
>>>> What's the name of our type of the basic installation policy?
>>>>
>>>> Don
>>>>
>>>> -----Original Message-----
>>>> Hi Don,
>>>>
>>>> Stephan has already described the way to implement different  
>>>> priority
>>>> jobs by defining new boolean resources and attaching them to  
>>>> different
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>> queues.
>>>>
>>>> However, your desire to have some "leakage" of medium and low  
>>>> priority
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>> jobs can be handled automatically through another policy: the
>>>> waiting-time weight.  By setting this to a non-zero value, it  
>>>> assures
>>>> that, the longer a job remains pending, the higher the priority that
>>>> it gets.  This automatically ensures that no job gets "forgotten"  
>>>> but
>>>> that, eventually, the job will have sufficiently high priority to go
>>>> next.
>>>> This in effect implements a "trickle-job" policy such as you want.
>>>>
>>>> Regards,
>>>>     Charu
>>>>
>>>>
>>>> On Jul 15, 2004, at 8:04 AM, Don Shesnicky wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> Chris/Stephan,
>>>>> Thank you very much for your replies, I've printed them out and  
>>>>> after
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>>> peeking, poking and doing some more reading I'm going to give some
>>>>> ideas a try. Right now I'm trying to setup a subordinate queue  
>>>>> where
>>>>> the submissions to the high priority queue will suspend the normal
>>>>> priority.
>>>>>
>>>>> The need in this case is for one group within our company where we
>>>>> are
>>>>>
>>>>>
>>>>> involved in chip design. The normal priority queue will be for run  
>>>>> of
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>>> the mill digital verification jobs but there can be a need to run a
>>>>> high priority job that is a rush and certain users will be given  
>>>>> the
>>>>> right to enter jobs in this queue. In addition we would like a low
>>>>> priority queue where certain back ground tasks can slowly work  
>>>>> their
>>>>> way through the system and may in fact have hosts in the queue that
>>>>> the others do not. In any case we would in some way like at least
>>>>> some
>>>>>
>>>>>
>>>>> of the low and normal priority queues to work their way through the
>>>>> system - some small leakage if you will.
>>>>>
>>>>> Don
>>>>>
>>>>> ------------------------------------------------------------------- 
>>>>> --
>>>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>>>> For additional commands, e-mail:  
>>>>> users-help at gridengine.sunsource.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ########################################################
>>>> # Charu V. Chaubal                           # Phone: (650) 786-7672
>>>> (x87672)
>>>> # Grid Computing Technologist        # Fax:   (650) 786-4591
>>>> # Sun Microsystems, Inc.                     # Email:
>>>> charu.chaubal at sun.com
>>>> ########################################################
>>>>
>>>>
>>>> -------------------------------------------------------------------- 
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>>>
>>>>
>>>> -------------------------------------------------------------------- 
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>>>
>>>>
>>>>
>>>>
>>>
>>> ########################################################
>>> # Charu V. Chaubal                            # Phone: (650) 786-7672
>>> (x87672)
>>> # Grid Computing Technologist # Fax:   (650) 786-4591
>>> # Sun Microsystems, Inc.                      # Email:
>>> charu.chaubal at sun.com
>>> ########################################################
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>>
>>>
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>
> --
> ####################################################################
> # Charu V. Chaubal              # Phone: (650) 786-7672 (x87672)   #
> # Grid Computing Technologist   # Fax:   (650) 786-4591            #
> # Sun Microsystems, Inc.        # Email: charu.chaubal at sun.com     #
> ####################################################################
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
########################################################
# Charu V. Chaubal				# Phone: (650) 786-7672 (x87672)
# Grid Computing Technologist	# Fax:   (650) 786-4591
# Sun Microsystems, Inc.			# Email: charu.chaubal at sun.com
########################################################


---------------------------------------------------------------------
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