[torqueusers] Problem with ppn and routing
garrick at usc.edu
Tue Nov 30 10:42:26 MST 2010
On Tue, Nov 30, 2010 at 10:42:56AM -0700, David Beer alleged:
> > >
> > > At some point (I believe 2.5) we added the ability to use
> > > resources_max.nodes in queue limitations, but it only sorts based on
> > > the number of nodes, not ppn. We couldn't sort based on ppn because
> > > of the inherent ambiguities - which is larger, nodes=1:ppn=2 or
> > > nodes=2:ppn=1 - so we only sort based on the first number there.
> > > This means that a job requesting nodes=1:ppn=2 will be accepted by
> > > the batch queue.
> > >
> > So now what does max/min.nodect mean?
> It is the same as always.
So now min/max.nodes is the same thing as min/max.nodect?
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California
Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20101130/5af4d41b/attachment.bin
More information about the torqueusers