Hey Sam,
The running times are not big O estimates:
The CPU version finished in 12 seconds.
The CPU-GPU-CPU version finished in 2.2 seconds.
The GPU version finished in 1.7 seconds.
I think there is something wrong with the netlib/cublas combination.
Sam already mentioned that cuBLAS doesn't
well, perhaps I just need to learn to use maven better, but currently I
find sbt much more convenient for continuously running my tests. I do use
zinc, but I'm looking for continuous testing. This makes me think I need
sbt for that:
bq. to be able to run my tests in sbt, though, it makes the development
iterations much faster.
Was the preference for sbt due to long maven build time ?
Have you started Zinc on your machine ?
Cheers
On Fri, Feb 27, 2015 at 11:10 AM, Imran Rashid iras...@cloudera.com wrote:
Has anyone else
Has anyone else noticed very strange build behavior in the network-*
projects?
maven seems to the doing the right, but sbt is very inconsistent.
Sometimes when it builds network-shuffle it doesn't know about any of the
code in network-common. Sometimes it will completely skip the java unit
Also, check the JNILoader output.
Remember, for netlib-java to use your system libblas all you need to do is
setup libblas.so.3 like any native application would expect.
I haven't ever used the cublas real BLAS implementation, so I'd be
interested to hear about this. Do an 'ldd
bq. I have to keep cd'ing into network/common, run mvn install, then go
back to network/shuffle and run some other mvn command over there.
Yeah - been through this.
Having continuous testing for maven would be nice.
On Fri, Feb 27, 2015 at 11:31 AM, Imran Rashid iras...@cloudera.com wrote: