lapack works best with an optimized blas, I used the
following for benchmark,
dgemm=: 'liblapack.so.3 dgemm_ > n *c *c *i *i *i *d *d *i *d *i *d *d *i'&cd
mm=: 4 : 0
k=. ,{.$x
c=. (k,k)$1.5-1.5
dgemm (,'N');(,'N');k;k;k;(,2.5-1.5);y;k;x;k;(,1.5-1.5);c;k
c
)
'A B'=:0?@$~2,,~4096
t1=: 6!:2'c1=: A+/ .*B'
echo ' GFlop ',~ 0j3": 2*(4096^3)%(t1)*1e9
t1=: 6!:2'c2=: A mm B'
echo ' GFlop ',~ 0j3": 2*(4096^3)%(t1)*1e9
echo c1-:c2
running dgemm on new hardware can get over 100 GFlop.
eg. j602 running on Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
0.879 GFlop
158.569 GFlop
1
Пт, 26 май 2017, Rudolf Sykora написал(а):
> On 26 May 2017 at 12:53, bill lam <[email protected]> wrote:
> > J depends on OS to locate the shared library. I think your
> > ldconfig cache did not include /usr/lib64/liblapack.so.3
> > or you may set LD_LIBRARY_PATH
> >
> > This is strange, if you had installed it from distro, ldconfig
> > should automatically run to add it into cache.
>
> Well, the problem eventually was not a missing /usr/lib64/liblapack.so.3,
> but missing libgfortran.so.3. Some update updated libgfortran to
> libgfortran.so.4,
> and thus broke a dependency of liblapack (ldd on it reveiled this).
> I just quickly copied .3 from a backup to /usr/lib64, and it now
> works.
>
> So cder'' was correct in saying *something* was missing, but
> it was not liblapack per se.
>
> Thanks for the help!
> Ruda
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
