<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Let me see if Mihael or I can add the ppn spec as a simple test to experiment with. I'll look for my coresPerNode mod which I think did this.<div><br></div><div>- Mike<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;">Hi Allan,<br><br>Yep, that's it. When the coasters resource request comes in with just "nodes=1", it gets interpreted by PBS as nodes=1:ppn=1, and thus PBS puts other jobs on the node, too, until all 8 CPUs are allocated (e.g., 8 1-cpu PBS jobs are running on it). <br>
<br>I'd like to find some way to make the request as:<br> nodes=1:ppn=8<br>along with<br> workersPerNode=8<br>so that PBS allocates one node and all 8 processors, and then one Coasters job would put 8 workers on it, matching the resource request with the use. <br>
<br>Matthew<br><br><br><br><br><div class="gmail_quote">On Wed, Nov 3, 2010 at 5:41 PM, Allan Espinosa <span dir="ltr"><<a href="mailto:aespinosa@cs.uchicago.edu" target="_blank">aespinosa@cs.uchicago.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;">
Hi Matthew,<br>
<br>
Does this mean, coasters will now submit nodes=1;ppn=1 and do node packing?<br>
<br>
If there is no node packing being initiated by PBS, you can just<br>
specify workersPerNode=8 . But then what you request to PBS is now<br>
different to what you actually use.<br>
<br>
-Allan<br>
<br>
2010/11/3 Matthew Woitaszek <<a href="mailto:matthew.woitaszek@gmail.com" target="_blank">matthew.woitaszek@gmail.com</a>>:<br>
<div><div></div><div class="h5">> Good afternoon,<br>
><br>
> Is there a way to update PBS resource requests when using coasters to supply<br>
> modified PBS resource strings such as "nodes=1:ppn=8"? (Or other arbitrary<br>
> resource requests, such as node properties?)<br>
><br>
> Of course, I'm just trying to get coasters to allocate all of the processors<br>
> on an 8-core node, using either the "gt2:gt2:pbs" or "local:pbs" provider.<br>
> Both submit jobs just fine. I found no discernible difference with the<br>
> "host_types" Globus namespace variable, presuming I'm setting it right.<br>
><br>
> The particular cluster I'm using allows node packing for users that run lots<br>
> of single-processor tasks, so without ppn, it will assume nodes=1,ncpus=1<br>
> and thus pack 8 jobs on each node before moving on to the next node. (I know<br>
> it won't be an issue at sites that make nodes exclusive. On this system, the<br>
> queue default is "nodes=1:ppn=8", but because coasters explicitly specifies<br>
> the number of nodes in its generated resource request, the ppn default seems<br>
> to get lost!)<br>
><br>
> I see that this has been discussed as far back as 2007, and I found Marcin<br>
> and Mike's previous discussion of the topic at<br>
><br>
> <a href="http://mail.ci.uchicago.edu/pipermail/swift-user/2010-March/001409.html" target="_blank">http://mail.ci.uchicago.edu/pipermail/swift-user/2010-March/001409.html</a><br>
><br>
> but there didn't seem to be any definitive conclusion. Any suggestions would<br>
> be appreciated!<br>
><br>
> Matthew<br>
><br>
<br>
</div></div><font color="#888888">--<br>
Allan M. Espinosa <<a href="http://amespinosa.wordpress.com" target="_blank">http://amespinosa.wordpress.com</a>><br>
PhD student, Computer Science<br>
University of Chicago <<a href="http://people.cs.uchicago.edu/%7Eaespinosa" target="_blank">http://people.cs.uchicago.edu/~aespinosa</a>><br>
</font></blockquote></div><br>
<br>_______________________________________________<br>Swift-user mailing list<br>Swift-user@ci.uchicago.edu<br>http://mail.ci.uchicago.edu/mailman/listinfo/swift-user</blockquote><br><span><br><br>-- <br><span name="x"></span>Michael Wilde<br>Computation Institute, University of Chicago<br>Mathematics and Computer Science Division<br>Argonne National Laboratory<br><span name="x"></span><br></span></div></div></body></html>