[GE users] how are soft resource request satisfied

Dr Ian C. Smith i.c.smith at liverpool.ac.uk
Fri May 21 10:24:35 BST 2004


Hi Charu,

Some additional info below:

--On 20 May 2004 14:35 -0700 Charu Chaubal <Charu.Chaubal at Sun.COM> wrote:

>
> On May 20, 2004, at 8:38 AM, Dr Ian C. Smith wrote:
>
>> Hi,
>>
>> Can anyone demystify how soft resource requests
>> are satisfied -- as usual the Sun documentation is about as much
>> use as a chocolate kettle. For example, say I have
>> three queues Queue_A, Queue_B, Queue_C and corresponding
>> resources Resource_A, Resource_B and Resource_C and I
>> request:
>>
>> # $ -soft -l ResourceA=value
>> # $ -soft -l ResourceB=value
>> # $ -soft -l ResourceC=value
>>
>> and value <= max( ResourceA, ResourceB, ResourceA ).
>>
>> Ideally the job would go to the queue which most closely
>> satisfies the requirement i.e. Queue_i where i minimises
>> ( Resource_i - value ) - or indeed any Queue_i where
>> i satisfies Resource_i >= value.
>>
>
> How have you defined the resources?  eg, values, relop, etc.

The values come from load sensors. The complexes are of the form:

#name            shortcut   type   value           relop requestable 
consumable default
#--------------------------------------------------------------------------
------------
ResourceA        ResourceA  INT    0               <=    YES         NO 
0

and are attached to the corresponding queues. All queues are specified in a 
list in the
job script:

#$ -q QueueA,QueueB,QueueC

The resource values appear to be correct when using 'qhost -F' but still I 
get jobs
going to queues which don't provide sufficient resources ( value < 
Resource_i )
because of the soft request. I would like this to happen only as a last 
resort.


>
>> Uunfortunately jobs seem to go to any queue on an
>> ad hoc basis. Is there any reason for this or anything
>> that can be done about it. A document describing how
>> exactly the scheduling algorithms work would be very useful
>> assuming that there are some - not just some cobbled together
>> code. As has been mentioned before the lack of any OR logic
>> in resource requests is an incredible oversight.
>>
>
> "OR" has been added to Grid Engine 6.0.  In Grid Engine 5.3, if you give
> a list of queues using the -q flag to qsub, this is implicitly an OR of
> the queue list.

Yes - but it would nice if this applied to resource requests with '-l', 
maybe
I'll have to go with 6.0 eventually.


thanks,

-ian.

> Regards,
> 	Charu
>
>
>> regards,
>>
>> -ian.
>>
>>
>> -----------------------------------
>> Dr Ian C. Smith,
>> e-Science team,
>> University of Liverpool
>> Computing Services Department,
>>
>>
>> ---------------------------------------------------------------------
>> 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