Next: In Case of Problems
Up: A Tool for Cluster
Previous: Running in Text Mode
- All tests are archived in the src directory.
- The bps suite is best run as a normal user, not root. Some of the
tests (i.e. NAS parallel) will not run as root.
- Not all features of the command line interface are possible with the
GUI.
- When using Netpipe and Netperf Benchmarks, rsh with no password must
be permitted between the nodes.
- Under normal operation, xbps will always preserve the existing log
directory. This feature is to ensure previous results will not be
overwritten. You can copy previous log files (from log directories)
into the current log directory for bps-html conversion.
- Also, the tests have been designed so that the BPS rpm only needs
to be installed on the master node. For this to work, the BPS log
directory must be mounted on all nodes (e.g. under /home).
- NAS Parallel Benchmarks have been tested with Paralogic's versions
of LAM and MPICH. Please see the NAS documentation for more information.
Rather than limit potential BPS users, these are not made a part of
the required packages list. The benchmark scripts have been written
to rely on the three environment variables (LAM_HOME for
LAM-MPI, MPICH_HOME for MPICH, and MPIPRO_HOME
for MPI-PRO, and MPICH). If you are having problems with the NAS benchmarks,
extract the npb.tar.gz archive in the/usr/bps/src directory and try
running the scripts manually (see below). Consult the README.plogic
file for more information. Also, if you wish to use the Portland Group
or the Intel Compilers make sure they are properly configured. Note:
on Paralogic clusters, these tests are designed to use modules for
easy transition from one MPI/Compiler version to another.
Next: In Case of Problems
Up: A Tool for Cluster
Previous: Running in Text Mode
Douglas Eadline
2003-03-17