Hi Abhi!<br><br><div class="gmail_quote">On Thu, Dec 16, 2010 at 2:32 PM, Abhishek Gupta <span dir="ltr"><<a href="mailto:abhig@princeton.edu">abhig@princeton.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Renato,<br>
Its not increasing memory, but if I say I need mem=6gb or pmem=6gb, it
still goes to the node with total memory less than 6gb. So I thought by
setting the NODEAVAILABILITYPOLICY, I will be able to define
availability on the bases of memory. <br>
Like we define np= in nodes file, do we have to define memory resources
too? <br>
Thanks,<br>
Abhi.</div></blockquote><div><br>I have been re-reading the documentation and I think every time what you are doing is correct and should work.<br><br>I have not set a NODEAVAILABILITYPOLICY for my site, and I have a nodeXXX which has 16GB of RAM. I tried running:<br>
<br>qsub -l pmem=4GB,host=nodeXXX sleep60job.sh<br>qsub -l pmem=4GB,host=nodeXXX sleep60job.sh<br>
qsub -l pmem=4GB,host=nodeXXX sleep60job.sh<br>
<br>And the three jobs ran on the same node, immediately (it was idle).<br><br>Then I tried:<br><br>qsub -l pmem=15GB,host=nodeXXX sleep60job.sh<br>
qsub -l pmem=15GB,host=nodeXXX sleep60job.sh<br>
qsub -l pmem=15GB,host=nodeXXX sleep60job.sh<br><br>And the first job ran, the others got queued, and then another ran, lefting the last one in the queue, and then the last one ran.<br><br>So, from my point of view, this is working. If you attempt to do something similar, where does it fail?<br>
<br>Cheers,<br>Renato.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000"><div><div></div><div class="h5">
<br>
Renato Borges wrote:
<blockquote type="cite">Hi Abhi!<br>
<br>
<div class="gmail_quote">On Wed, Dec 15, 2010 at 7:21 PM, Abhishek
Gupta <span dir="ltr"><<a href="mailto:abhig@princeton.edu" target="_blank">abhig@princeton.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
I am trying to figure out the way so that memory usage does not exceed<br>
the available memory on a node. I was thinking that this parameter (<br>
NODEAVAILABILITYPOLICY COMBINED:MEM ) should check the availability of<br>
node on the bases of memory available, but it does not.<br>
Is there anything else I need to add to make it work?<br>
NODEAVAILABILITYPOLICY COMBINED:MEM<br>
<br>
Thanks,<br>
Abhi.<br>
</blockquote>
<div><br>
I´ve never used NODEAVAILABILITYPOLICY, but I have a similar problem,
which is: the jobs we run at my site start out with a small memory
footprint, and end with large amounts of data in memory (in
virtualization lingo, they "balloon"). Maybe this is also your case,
and this is why setting this variable doesn`t work?<br>
<br>
To avoid swapping, I have set a MAXJOBPERUSER variable for each compute
node, because all of our jobs that have an increasing memory footprint
come from a single user (actually, a grid account).<br>
<br></div></div></blockquote></div></div></div></blockquote></div>(...)<br clear="all"><br>-- <br>Renato Callado Borges<br>Lab Specialist - DFN/IF/USP<br>Email: <a href="mailto:rborges@dfn.ifusp.br" target="_blank">rborges@dfn.ifusp.br</a><br>
Phone: +55 11 3091 7105<br>