Re: [Numpy-discussion] Accelerate or OpenBLAS for numpy / scipy wheels?

2016-07-01 Thread Sturla Molden
Ralf Gommers wrote: > Thanks Sturla, interesting details as always. You didn't state your > preference by the way, do you have one? I use Accelerate because it is the easier for me to use when building SciPy. But that is from a developer's perspective. As you know, Accelerate breaks a common (a

Re: [Numpy-discussion] Accelerate or OpenBLAS for numpy / scipy wheels?

2016-07-01 Thread Ralf Gommers
On Wed, Jun 29, 2016 at 11:06 PM, Sturla Molden wrote: > Ralf Gommers wrote: > > > For most routines performance seems to be comparable, and both are much > > better than ATLAS. When there's a significant difference, I have the > > impression that OpenBLAS is more often the slower one (example:

Re: [Numpy-discussion] Accelerate or OpenBLAS for numpy / scipy wheels?

2016-07-01 Thread Sturla Molden
On 29/06/16 21:55, Nathaniel Smith wrote: Speed is important, but it's far from the only consideration, especially since differences between the top tier libraries are usually rather small. It is not even the more important consideration. I would say that correctness matters most. Everything

Re: [Numpy-discussion] Accelerate or OpenBLAS for numpy / scipy wheels?

2016-07-01 Thread Sturla Molden
On 29/06/16 21:55, Nathaniel Smith wrote: Accelerate is closed, so when we hit bugs then there's often nothing we can do except file a bug with apple and hope that it gets fixed within a year or two. This isn't hypothetical -- we've hit cases where accelerate gave wrong answers. Numpy actually c