On Wed, May 26, 2010 at 7:16 PM, Mark A Saper <span dir="ltr">&lt;<a href="mailto:saper@umich.edu">saper@umich.edu</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div>Interestingly, although each node has 8 processors, the OMIT region jobs seems to only use one processor!  </div></div></blockquote><div><br></div><div>The individual jobs spawned by AutoBuild are single-processor; the queueing system may have spread them out over as many nodes as possible, but they could just as well run on all 8 processors of one node, as long as enough memory is available.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div>Interestingly when phenix.refine jobs are run on my Macbook Pro, the operating system is savvy enough to spread it over 2 processors.</div>
</div></blockquote><div><br></div><div>phenix.refine itself isn&#39;t actually using both processors at once, though - I&#39;m not sure how Python and the OS work internally, but only one Python or C++ thread is running at a time, and it may switch between processors.  (I&#39;ve noticed the same behavior on my Macs.)  If you use the GUI, that will be running in a separate process, but it doesn&#39;t do very much other than process messages from phenix.refine, plus whatever is required to display the model and maps (if you watch them in Coot, etc.).</div>
<div><br></div><div>-Nat</div></div>