<div dir="ltr">10 processes is quite easy to reach. There are:<div><br></div><div>- make</div><div>- bash</div><div>- perl (for Cactus preprocessing)</div><div>- cc (driver)</div><div>- cc1 (actual compiler)</div><div>- as</div><div><br></div><div>and then there might be:</div><div><br></div><div>- another make (there's one per thorn)</div><div>- another bash</div><div><br></div><div>etc. etc.</div><div><br></div><div>-erik</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 16, 2016 at 10:55 AM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@cct.lsu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Dec 13, 2016 at 02:30:32PM -0600, Roland Haas wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
rhaas@login3:~/tmp$ ulimit -a | grep processes<br>
max user processes (-u) 150<br>
<br>
which is reached (in my case) when compiling with the default -j<br>
settings in simfactory on stampede (somewhere in PeTSc).<br>
</blockquote>
<br></span>
Since I had to look it up and others might want the same: stampede is currently configured to use<br>
make -j8<br>
which is reasonable, I believe.<br>
<br>
And: 150 is indeed quite low. Maybe it would make sense to ask them to increase this a little if you can show that it does hamper parallel compilation.<br>
<br>
Nevertheless, I am surprised that you reach 150 processes with just 8 parallel make sessions. Assuming you got some 'background' processes just by logging in, that would probably still mean more than 10 processes per make, which sounds high. Do you know why that number is so high?<br>
<br>
I also compiled a lot on stampede lately. I've never seen that problem. Could it be that your limit of 150 is taken by something else than the processes spawned by make?<br>
My "problem" on stampede is the limit of 5GB home. Despite $WORK being said to be optimized for large files, they advised me to compile there if $HOME isn't big enough. 5GB is already too small for two configurations...<span class="HOEnZb"><font color="#888888"><br>
<br>
Frank<br>
<br>
</font></span><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.einsteintoolkit.<wbr>org/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a></div>
</div>