[GE users] h_vmem, virtual_free

Heywood, Todd heywood at cshl.edu
Fri Feb 23 19:23:22 GMT 2007


Sorry, shot that off too soon. To answer my own question: because h_vmem
is set to "INFINITE" for my queues? If h_vmem is a queue attribute, and
my queues contain nodes of varying amounts of memory, this would mean I
can't use h_vmem for requesting memory.

Todd

-----Original Message-----
From: Heywood, Todd [mailto:heywood at cshl.edu] 
Sent: Friday, February 23, 2007 1:57 PM
To: users at gridengine.sunsource.net
Subject: RE: [GE users] h_vmem, virtual_free

Thanks. So, why does SGE run a job with a request of "-l h_vmem=4G" on a
node which has (<) 2GB of real memory?

Todd

-----Original Message-----
From: Sean Dilda [mailto:sean at duke.edu] 
Sent: Friday, February 23, 2007 1:52 PM
To: users at gridengine.sunsource.net
Subject: Re: [GE users] h_vmem, virtual_free

Heywood, Todd wrote:

> 
> I'm really unclear on what h_vmem does. I thought it was a requestable
> resource, and setting it wouldn't change anything on the nodes.

You're kinda right.   Sometime most people don't realize is that h_vmem 
does change the hard vmem ulimit/rlimit    So, whenever you set these 
values on a queue, or request one of them, they set the ulimit/rlimit 
for the job.


This is true for all of the h_ (for hard) and s_ (for soft) attributes.

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




More information about the gridengine-users mailing list