1 |
Hello all. |
2 |
This week the automated benchmarking suite project has received much |
3 |
work. During the first half of the week I |
4 |
|
5 |
* improved the HTML report |
6 |
* closed a number of bugs |
7 |
* implemented a module for testing FFTW |
8 |
|
9 |
Then, I spent a couple of days investigating the distributed-memory |
10 |
parallel routines of BLACS, PBLAS and ScaLAPACK, and their |
11 |
availability in Gentoo. I also set up an MPI environment under Gentoo |
12 |
and decided to share my experience within the documentation of Gentoo, |
13 |
which is slightly outdated. |
14 |
|
15 |
Now, some work is being done in the pkg-config interface of the |
16 |
script. Pkg-config is used by the script to retrieve the compile |
17 |
instructions when compiling and linking against the numerical |
18 |
libraries. The new alternatives-2 system relies on this useful tool, |
19 |
and the benchmarking project also does. Some refinement will allow the |
20 |
user to customize even more the tests. |
21 |
|
22 |
|
23 |
Implementing a module for testing FFTW |
24 |
======================================== |
25 |
|
26 |
This field is a bit special, as FFTW is not a standard which is |
27 |
reimplemented in optimized libraries (which is the case of BLAS, |
28 |
CBLAS, LAPACK,...). However, it is useful to compare the speed of FFTW |
29 |
compiled with different compilers, versions or flags, so there is a |
30 |
particular module for testing this widely used library. |
31 |
|
32 |
FFTW can perform a wide number of tasks, and a survey has been taken |
33 |
[1] asking the community about the most wanted tests. Following the |
34 |
results, the following tests have been implemented: |
35 |
* Forward Discrete Fourier Transormation |
36 |
* Backward Discrete Fourier Transormation |
37 |
* The same two with the flag FFTW_MEASURE instead of FFTW_ESTIMATE |
38 |
|
39 |
After the mid-term evaluation also 2-dimensional tests will be |
40 |
provided. Now this four tests are available and implemented within the |
41 |
BTL framework, which makes the benchmarking suite robust. The tests |
42 |
until now have been successful. |
43 |
|
44 |
|
45 |
Next week's milestones |
46 |
======================== |
47 |
|
48 |
The mid-term evaluation will come soon. For this, I'm performing many |
49 |
tests in order to present, as mid-term result, a general comprehensive |
50 |
report which makes clear that the project is already usable. My mentor |
51 |
reported that my script already allowed him to find some bugs in a |
52 |
package, which already is a good results for me -- even if the purpose |
53 |
of the script is not (only) finding bugs --. My mid-term report will |
54 |
hopefully persuade many people to run some benchmarks on their |
55 |
computers. |
56 |
|
57 |
So, objectives for the next week are: |
58 |
|
59 |
* Improve the pkg-config interface |
60 |
* Improve the user configuration possibilities |
61 |
* Improve the niceness and information of the HTML reports |
62 |
* Test the suite as much as possible in order to generate a |
63 |
comprehensive set of reports for each supported library (BLAS, CBLAS, |
64 |
LAPACK, FFTW) |
65 |
|
66 |
|
67 |
Best regards |
68 |
Andrea Arteaga |
69 |
|
70 |
|
71 |
[1] https://spreadsheets.google.com/spreadsheet/viewform?hl=en_US&formkey=dGlKbjBfLW5uaGt4QnQxNFJYUVp1QlE6MQ#gid=0 |