Re: [PerfSuite-users] mpirun with perfsuite

[Rick K. <rk...@nc...>]

On Wed, 7 Dec 2005, Giuseppe Grieco wrote:

> Dear Rick,
> I tried to run =A0
>=20
>  % /usr/local/mpich-1.2.7/bin/mpirun -np 2 /usr/local/bin/psrun cpi-mpi
>=20
> as I have ch_p4 device for MPICH installed. As soon as I will try the o=
ther way you suggested me, I will let you know the result.
> Now I would like to make you another question:
> in an old mail I asked you if it was possible install perfsuite with di=
fferent fortran compilers and part of your answer was:
>=20
> [ ... ]
>=20
> I receive errors. I try to install perfsuite with mpich that has differ=
ent installation for GNU compilers and intel compilers. So when I set MPI=
CPPFLAGS for step 4 is different than for step 1. Does it cause problems?=
 If yes, is it possible to install different versions of perfsuite, as fo=
r mpich?
> Always thanks for your support.

Giuseppe,

Since you are using MPICH ch_p4, I would guess that psrun will not be=20
effective for you for the reasons that I mentioned previously (command=20
line getting mangled).

Regarding how to install multiple versions of PerfSuite on one system,=20
each using different configuration options: PerfSuite uses GNU Autotools=20
for its build system, and that is quite flexible, so most combinations ar=
e=20
possible and should work with multiple Fortran compilers, multiple MPI=20
implementations, etc.  The primary limitation is on how much disk space=20
you can afford to use for each additional installation.

We routinely use multiple compiler vendors (GNU, Intel, Open64), and=20
multiple MPI implementations (MPICH ch_p4/GM, ChaMPIon/Pro), so it is=20
definitely possible to do this, but does take some planning and=20
familiarity with software installation, calling conventions, etc.=20

Probably the most straightforward way to maintain different versions of=20
PerfSuite is to use a distinct "--prefix" option for each variant.  For=20
example, let's say you want GNU and Intel compiler support with MPICH and=
=20
LAM as MPI layers and you want to mix and match.  This would be a total o=
f=20
4 combinations.  You could do:

./configure --prefix=3D/opt/perfsuite-gnu-mpich --enable-mpi \
    MPICPPFLAGS=3D"-I/opt/mpich/include"
make && make install

./configure --prefix=3D/opt/perfsuite-gnu-lam --enable-mpi \
    MPICPPFLAGS=3D"-I/opt/lam/include"
make && make install

./configure --prefix=3D/opt/perfsuite-intel-mpich --enable-mpi \
    MPICPPFLAGS=3D"-I/opt/mpich/include" F77=3Difort
make && make install

./configure --prefix=3D/opt/perfsuite-intel-lam --enable-mpi \
    MPICPPFLAGS=3D"-I/opt/lam/include" F77=3Difort
make && make install

To use any one of these versions, you would then have to make sure you=20
have "source"d the proper "psenv" script and probably have to arrange for=
=20
PATH/LD_LIBRARY_PATH settings so that remote MPI tasks, when launched=20
through rsh or ssh are set properly.  There are numerous site-specific=20
things that are likely to crop up, and for that you have to use some=20
investigative skills to resolve.

Please note that it is <mpi.h> and the setting of F77 that is most=20
relevant to the PerfSuite library.  It is up to the user and/or the mpicc=
=20
or mpif77 command to select the proper MPI library itself when building a=
n=20
MPI application.  That is, nothing in the PerfSuite build actually links=20
with an existing MPI library... this is deferred until the MPI applicatio=
n=20
is actually built or run.

I would say that, for the person just getting started using PerfSuite,=20
it's probably easiest to choose just one preferred Fortran compiler and=20
MPI installation and work exclusively with that first, so that you can ge=
t=20
familiar with PerfSuite and MPI without worrying about multiple installat=
ions. =20
Then once you have the basics down, expand to additional versions as=20
needed.

Good luck,
Rick