[GE users] subordination and memory oversubscription

rdickson ross.dickson at dal.ca
Thu Mar 5 20:28:52 GMT 2009


Hmm, RQS.  I'll give that a try.  Thanks, Reuti!

- Ross


reuti wrote:
> Hi,
>
> Am 04.03.2009 um 16:23 schrieb rdickson:
>
>   
>>  Can anyone suggest a way we can dodge
>> those two risks?
>>
>>     1) With exechost h_vmem set to physical RAM, superordinate jobs  
>> can
>> be prevented from scheduling by the subordinate queue "sitting on" the
>> h_vmem.
>>
>>     2) With exechost h_vmem set to greater than physical RAM, a single
>> queue can oversubscribe memory on a machine.
>>     
>
> instead defining h_vmem as complex_value in the exechost  
> configuration (which is working fine and was the proper setting in  
> the past), you can nowadays put this limit also in an RQS. And in  
> this you can define two rules, one for each queue.
>
> limit queues onequeue hosts {*} to h_vmem=8G
> limit queues anotherqueue hosts {*} to h_vmem=8G
>
> -- Reuti
>

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=121538

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list