expected performance and fortran interface

[faircdl]

Here are some run times:

5000x5000 matrix solve via sgesv on corei7:
ATLAS 1 thread - 5.5s
ATLAS auto thread - 2.12
PLASMA+ATLAS with optimal block size, 1 thread - 15.27
PLASMA+ATLAS with optimal block size, 4 thread - 3.93

10000x10000:
ATLAS auto thread - 12.92
PLASMA+ATLAS with optimal block size, 4 thread - 30.78
MKL auto thread - 8.62
PLASMA+MKL (MKL_NUM_THREAD=1), 4 thread - 12.07

Perhaps I'm just not going to see big gains from PLASMA unless I run on a many-core machine. This is always the situation shown in the various graphs I've seen...machines with 16-64 cores rather than 4-8.

[mateo70]

Hi,

sorry to answer so late to your problem, but do you still have your segfault when you are using fortran interface ?
Because I guess your system is a 64bits one, so normally pointer are 64bits and you should use INTEGER*8 instead of INTEGER*4 in your call to Plasma.

Mathieu

[faircdl]

Yes, I am still having a segfault for the fortran interface. I used INTEGER*8 as the type. I put some print statements in the PLASMA routine, and the segfault is occurring in PLASMA somewhere beyond the C-wrapper function that fortran is calling. But I may still be doing something wrong.

[mateo70]

Ok, I will try to reproduce the problem to see what is it.

[slemons]

I would be very interested to get your tests when you finish them(or even before). I am hoping to test lapack calling threaded blas and plasma. This fortran interface problem is something i would almost certainly run into if i tried this on my own, so thanks for that too!

how many cores do you expect to need before you see a big improvement?