[torqueusers] Problem with ppn and routing
dbeer at adaptivecomputing.com
Tue Nov 30 10:42:56 MST 2010
> > 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.
More information about the torqueusers