[torqueusers] Problem with ppn and routing

David Beer dbeer at adaptivecomputing.com
Tue Nov 30 10:45:52 MST 2010



----- Original Message -----
> 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?
> 

Yes, they do the exact same thing. We did this because we were asked for it over and over again, and it wasn't hard to add.

David


More information about the torqueusers mailing list