root / INSTALL @ 9
Historique | Voir | Annoter | Télécharger (3,02 ko)
1 |
============================================================== |
---|---|
2 |
High Performance Computing Linpack Benchmark (HPL) |
3 |
HPL 2.0 - September 10, 2008 |
4 |
============================================================== |
5 |
|
6 |
1) Retrieve the tar file, then |
7 |
|
8 |
gunzip hpl.tgz; tar -xvf hpl.tar |
9 |
|
10 |
this will create an hpl directory, that we call below the |
11 |
top-level directory. |
12 |
|
13 |
2) Create a file Make.<arch> in the top-level directory. For |
14 |
this purpose, you may want to re-use one contained in the |
15 |
setup directory. This file essentially contains the compilers |
16 |
and librairies with their paths to be used. |
17 |
|
18 |
3) Type "make arch=<arch>". This should create an executable |
19 |
in the bin/<arch> directory called xhpl. |
20 |
|
21 |
For example, on our Linux PII cluster, I create a file called |
22 |
Make.Linux_PII in the top-level directory. Then, I type |
23 |
"make arch=Linux_PII" |
24 |
This creates the executable file bin/Linux_PII/xhpl. |
25 |
|
26 |
4) Quick check: run a few tests: |
27 |
|
28 |
cd bin/<arch> |
29 |
mpirun -np 4 xhpl |
30 |
|
31 |
5) Tuning: Most of the performance parameters can be tuned, |
32 |
by modifying the input file bin/HPL.dat. See the file TUNING |
33 |
in the top-level directory. |
34 |
|
35 |
============================================================== |
36 |
|
37 |
Compile time options: At the end of the "model" Make.<arch>, |
38 |
--------------------- the user is given the opportunity to |
39 |
compile the software with some specific compile options. The |
40 |
list of this options and their meaning are: |
41 |
|
42 |
-DHPL_COPY_L |
43 |
force the copy of the panel L before bcast; |
44 |
|
45 |
-DHPL_CALL_CBLAS |
46 |
call the cblas interface; |
47 |
|
48 |
-DHPL_CALL_VSIPL |
49 |
call the vsip library; |
50 |
|
51 |
-DHPL_DETAILED_TIMING |
52 |
enables detail timers; |
53 |
|
54 |
The user must choose between either the BLAS Fortran 77 |
55 |
interface, or the BLAS C interface, or the VSIPL library |
56 |
depending on which computational kernels are available on his |
57 |
system. Only one of these options should be selected. If you |
58 |
choose the BLAS Fortran 77 interface, it is necessary to fill |
59 |
out the machine-specific C to Fortran 77 interface section of |
60 |
the Make.<arch> file. To do this, please refer to the |
61 |
Make.<arch> examples contained in the setup directory. |
62 |
|
63 |
By default HPL will: |
64 |
*) not copy L before broadcast, |
65 |
*) call the BLAS Fortran 77 interface, |
66 |
*) not display detailed timing information. |
67 |
|
68 |
As an example, suppose one wants HPL to copy the panel of |
69 |
columns into a contiguous buffer before broadcasting. In |
70 |
theory, it would be more efficient to let HPL create the |
71 |
appropriate MPI user-defined data type since this may avoid |
72 |
the data copy. So, it is a strange idea, but one insists. To |
73 |
achieve this one would add -DHPL_COPY_L to the definition of |
74 |
HPL_OPTS at the end of the file Make.<arch>. Issue then a |
75 |
"make clean arch=<arch>; make build arch=<arch>" and the xhpl |
76 |
executable will be re-build with that feature in. |
77 |
============================================================== |
78 |
|
79 |
Check out the website www.netlib.org/benchmark/hpl for the |
80 |
latest information. |
81 |
============================================================== |