[philipkglass]

I'd like to see benchmarks with OpenBLAS. Unlike ACML it's under active development, unlike MKL it won't deliberately screw AMD performance, and it offers "pretty good" performance across every environment I've tried it in. Good enough that it's not worth paying for MKL, not worth going through ATLAS's self-tuning routine, not worth changing my build scripts to use vecLib under OS X. If OpenBLAS currently runs poorly on Ryzen I hope Ryzen will get some development love, because I kind of hate using ATLAS and at this point it would take a major advantage to tempt me back away from open source components.

[timeu]

Word! I think AMD should focus on OpenBLAS and add support for their new CPUs there. OpenBLAS is part of the foss toolchain for the easybuild easyconfig. So for the HPC field adding support to OpenBLAS would be great.

I would also need to update this benchmark (if I can get hold of the new AMD CPUs) ;-) http://stackoverflow.com/questions/5260068/multithreaded-bla...

[gcp]

OpenBLAS performance is atrocious in 32 bit mode because it doesn't properly support AVX with the halved register file. Not the most common configuration, but MKL handles it fine (on Intel chips, obviously).

That said I agree it makes more sense for AMD to contribute to OpenBLAS than anything else.

[philipkglass]

Interesting -- what are the use cases for single precision BLAS on CPU? All the scientific software I use requires double precision and for tasks that do well with single precision, I would have thought that GPGPU would now be the go-to solution.

[gcp]

Not if you're shipping software to consumers. (Also, I actually meant 32-bit as in the OS, not the floating point precision)