[torquedev] nodes, procs, tpn and ncpus

Ken Nielson knielson at adaptivecomputing.com
Wed Jun 9 08:44:15 MDT 2010

On 06/09/2010 08:37 AM, Martin Siegert wrote:
>> nodes=x:ppn=x will work as it currently does except that the value for nodes will not be ignored.
>> That is a node spec of -l nodes=2:ppn=2 will look for two nodes with two available processors. This can be satisfied on the same host or different hosts. Currently this node spec will only get two processors on a single node.
> we worked hard to teach our users that nodes=x:ppn=y does exactly what it
> says, namely it gives you x nodes with y processors each: ppn meaning
> processors-per-node, i.e., ppn=2 gives you two processors per node, not 4
> or 6 or 8. Ever since procs was introduced we have been using
> and it would be very difficult for us if that meaning would change.
The changes to TORQUE would not change Moab behavior. If you are using 
Moab and the JOBNODEMATCHPOLICY EXACTNODE it will still behave the same.

The changes to TORQUE just allow TORQUE to interpret resource requests 
in the absence of a scheduler.


More information about the torquedev mailing list