mpiexec smp runs.

[Chris Samuel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 29 Aug 2003 08:27 am, Amitoj Singh wrote:

Caveat: We're running Scalable PBS rather than the defunct OpenPBS.

>    We are running OpenPBS 2.3.16 with mpiexec Version 0.74.
> Non-smp jobs run fine. But for smp runs i gather we need to launch a jobs
> as follows ..
>
>    qsub -l nodes=4:ppn=2 <pbsscript>

That is correct.

>   If yes, then we have a problem because we define our nodes as single
> processor "np=1"  nodes. The reason behind this is that we wish to restrict
> PBS from trying to launch more than one different process per node. For eg.
> if job xyz is using 4 nodes then we wish the nodes to be job-exclusive to
> job xyz. And so the above qsub command fails.

If you define your nodes as dual processor nodes then the above command should 
allocate them as job-exclusive.  What problems were you seeing that forced 
you to make that change ?

Some of that is conditional on the scheduler you are using, are you using 
pbs_sched or MAUI ?

The pbs_sched will handle it fine, but with MAUI it might try and be clever 
and judge where to run jobs based on the load average of the node. You can 
tell MAUI to honour PBS's decision by specifying the following in your 
maui.cfg:

# Force MAUI to comply with PBS's policy of nodes and jobs
JOBNODEMATCHPOLICY      EXACTNODE

>    We are currently using mpirun to launch jobs at our site. We had changed
> the mpirun script to launch smp jobs at our site (by editing the file
> PBS_NODEFILE to have each node appear twice for an smp job), but with
> mpiexec this seems impossible. Any help in this regard will be much
> appreciated.

Hopefully the above will help!

cheers,
Chris
- -- 
 Christopher Samuel - (03)9925 4751 - VPAC Systems & Network Admin
 Victorian Partnership for Advanced Computing http://www.vpac.org/
 Bldg 91, 110 Victoria Street, Carlton South, VIC 3053, Australia

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/TpJvO2KABBYQAh8RAo//AJ9mDOwehnz0X2l9lqDgVtLy2k22gACdFWNM
7cY2J1B90+v0M9Twzei6KIk=
=aaGx
-----END PGP SIGNATURE-----