[torquedev] nodes, procs, tpn and ncpus

Ken Nielson knielson at adaptivecomputing.com
Wed Jun 9 16:22:11 MDT 2010

On 06/09/2010 03:48 PM, Ken Nielson wrote:
> On 06/09/2010 03:05 PM, Glen Beane wrote:
>> I don't believe I have anything else going on.  You have been wrong on
>> the behavior of other specs, like nodex=X:ppn=Y only allocating one
>> node. It appears you have something else going on than every other
>> TORQUE user.
>> I can't gdb pbs_server on a production cluster to see where I am
>> different, maybe someone else can do that on a test cluster.
>> Anyway, the behavior you are seeing is not correct. It is either a bug
>> in torque or a problem with your setup.
>> _______________________________________________
> We figured it out. The difference is I have "set server
> resources_available.nodect = 1024" in my  configuration and you do not.
> This sets the global SvrNodeCt which affects the behavior. Why it does
> is my next task.
> Ken
With this discovery I have found that TORQUE interprets nodes to be 
separate hosts.

So -l nodes=3 <job.sh> will allocate three different hosts for the job 
making the behavior of nodes different the procs.


More information about the torquedev mailing list