[torqueusers] strange behaviour of ppn

Andrus, Brian Contractor bdandrus at nps.edu
Mon Nov 15 10:53:25 MST 2010


Govind,
 
You may want to add:

#PBS -l naccesspolicy=singlejob
 
This will cause allocation to be a single job per node.
Given your resource request, you do not specify you need exclusive use of the node, so as far as torque is concerned, there are processors available to be assigned to jobs, which it does. 
 
Brian Andrus
 
 

________________________________

From: torqueusers-bounces at supercluster.org on behalf of Govind Songara
Sent: Fri 11/12/2010 8:25 AM
To: Torque Users Mailing List
Subject: [torqueusers] strange behaviour of ppn


Hi,


I am not expert on torque configurations, so might something wrong with configurations.
I am seeing a strange behaviour of ppn variable.
My nodes config is something like
node01 np=4
node02 np=4

snippet of maui config
JOBNODEMATCHPOLICY     EXACTNODE
ENABLEMULTINODEJOBS   TRUE
NODEACCESSPOLICY         SHARED


snippet of queue config
        resources_available.nodect = 65
        resources_assigned.nodect = 5
        resources_default.nodes = 1

sample script 
------------------------------------
#PBS -q long
#PBS -l nodes=2:ppn=1

echo This jobs runs on the following processors:
echo `cat $PBS_NODEFILE`
NPROCS=`wc -l < $PBS_NODEFILE`
echo This job has allocated $NPROCS processors
hostname
------------------------------------

Below is my result in the tables 


		
nodes

ppn

no. process run (hostname)

no. pf processor allocated

3

1

1

3

3

2

1

2

3

3

1

3

3

4

1

4

In case 1, it gives 3 processor on same node which is incorrect, it should give 1 processor on 3 different nodes
In case2, it give only 2 processor on same node, it should 2 processor on 3 different nodes (total 6 processor) and similar behaviour with the last tow cases.
In all the cases the hostname command run only once, which should run at least on total number of allocated processors.


Due to this strange behaviour i can not run mpi jobs correctly, kindly advise on this problem.

TIA

Regards
Govind





-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6979 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20101115/28f18eaa/attachment-0001.bin 


More information about the torqueusers mailing list