|
Size: 1710
Comment:
|
Size: 1536
Comment: Informationen über die alten Cluster entfernt
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| At Zeuthen a cluster of 16 dual opteron machines is available. It is integrated into the SGE batch system. The documentation in ["Batch System Usage"] applies to it. | There are no dedicated parallel clusters available at the moment, but you can run parallel MPI jobs in the SGE farm. The documentation in [[Batch_System_Usage]] applies there. |
| Line 6: | Line 6: |
| Since SL5, all batch worker nodes have the openmpi implementation of the MPI standard installed. | |
| Line 7: | Line 8: |
| Applications for the cluster must be compiled on a 64 bit machine, at the moment, this means either lx64 or linfini. There are MPI versions for the GCC, Intel and PGI compilers installed: | There are MPI versions for the GCC, Intel and PGI compilers installed: |
| Line 9: | Line 10: |
| /usr/local/ibgd/mpi/osu/gcc/mvapich-0.9.5/bin/mpicc | /opt/openmpi/gcc/bin/mpicc |
| Line 11: | Line 12: |
| /usr/local/ibgd/mpi/osu/intel/mvapich-0.9.5/bin/mpicc | /opt/openmpi/intel/bin/mpicc |
| Line 13: | Line 14: |
| /usr/local/ibgd/mpi/osu/pgi/mvapich-0.9.5/bin/mpicc |
/opt/openmpi/pgi/bin/mpicc |
| Line 18: | Line 18: |
=== Building applications === MPI Applications can be compiled on any 64 bit SL5 machine, e.g. sl5-64.ifh.de. |
|
| Line 23: | Line 26: |
| #$ -pe mpich-ppn2 4 | #$ -pe multicore-mpi 4 |
| Line 25: | Line 28: |
| It is important to request the right limit for memory with the parameter h_vmem. The machines have 3673204k of RAM and by default two jobs are executed on one node, so the maximal amount of memory is 1650M per process. | Be sure to call the right mpirun version for your compiler. If you application was compiled with GCC, use /opt/openmpi/gcc/bin/mpirun -np $NSLOTS yourapp |
| Line 31: | Line 37: |
| Be aware that the batch system renews the AFS token, but only on the node that starts the first process (node 0). That's why you should access the AFS from that node. An example scenario looks like this: | == BLAS library == Both ATLAS ans Goto``BLAS are available. |
| Line 33: | Line 40: |
| 1. Copy data from AFS to node 0. 1. Copy it with scp to the nodes that need it to the directory $TMPDIR, the machine names are in $TMPDIR/machines 1. Run your MPI job. 1. Copy the results with scp from the local discs to node 0. 1. Copy the data from node 0 to AFS. |
* ATLAS is in /opt/products/atlas * libgoto is in /usr/lib or /usr/lib64 respectively. == Further documentation == [[http://www-zeuthen.desy.de/technisches_seminar/texte/Technisches_Seminar_Waschk.pdf|HPC-Clusters at DESY Zeuthen]] , 11/22/06, technical seminar |
Usage of the Linux Clusters at DESY Zeuthen
There are no dedicated parallel clusters available at the moment, but you can run parallel MPI jobs in the SGE farm. The documentation in Batch_System_Usage applies there.
Building Applications
Since SL5, all batch worker nodes have the openmpi implementation of the MPI standard installed.
There are MPI versions for the GCC, Intel and PGI compilers installed:
/opt/openmpi/gcc/bin/mpicc
/opt/openmpi/intel/bin/mpicc
/opt/openmpi/pgi/bin/mpicc
Compilers for C++ and Fortran are available as well.
Building applications
MPI Applications can be compiled on any 64 bit SL5 machine, e.g. sl5-64.ifh.de.
Batch System Access
A job script designated for a parallel job needs to specify the parallel environment and the number of required CPUs. The parameter looks like this:
#$ -pe multicore-mpi 4
Be sure to call the right mpirun version for your compiler. If you application was compiled with GCC, use
/opt/openmpi/gcc/bin/mpirun -np $NSLOTS yourapp
AFS Access
The application binary must be available to all nodes, that's why it should be placed in an AFS directory.
BLAS library
Both ATLAS ans GotoBLAS are available.
- ATLAS is in /opt/products/atlas
- libgoto is in /usr/lib or /usr/lib64 respectively.
Further documentation
HPC-Clusters at DESY Zeuthen , 11/22/06, technical seminar