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

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] Benchmark regression feeds

Thanks Pauli! Maybe it's worth to add these to the devdocs pages? On Jun 24, 2016 10:05 PM, "Pauli Virtanen" wrote: > Hi, > > In case someone is interested in getting notifications of performance > regressions in the Numpy and Scipy benchmarks, this is available as Atom > feeds at:

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

On Jun 29, 2016 2:49 AM, "Andrew Jaffe" wrote: > > On 28/06/2016 18:50, Ralf Gommers wrote: >> >> >> On Tue, Jun 28, 2016 at 5:50 PM, Chris Barker > > wrote: >> >> > This doesn't really matter too much imho, we

Re: [Numpy-discussion] Is numpy.test() supposed to be multithreaded?

On Mi, 2016-06-29 at 02:03 -0700, Nathaniel Smith wrote: > As a general rule I wouldn't worry too much about test speed. Speed > is > extremely dependent on exact workloads. And this is doubly so for > test > suites -- production workloads tend to do a small number of normal > things over and

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

On 28/06/2016 18:50, Ralf Gommers wrote: On Tue, Jun 28, 2016 at 5:50 PM, Chris Barker > wrote: > This doesn't really matter too much imho, we have to support Accelerate > either way. do we? -- so if we go OpenBlas, and

Re: [Numpy-discussion] Is numpy.test() supposed to be multithreaded?

As a general rule I wouldn't worry too much about test speed. Speed is extremely dependent on exact workloads. And this is doubly so for test suites -- production workloads tend to do a small number of normal things over and over, while a good test suite never does the same thing twice and spends

Re: [Numpy-discussion] Is numpy.test() supposed to be multithreaded?

On Wed, Jun 29, 2016 at 3:27 AM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > > >> Now the user is writing back to say, "my test code is fast now, but >> numpy.test() is still about three times slower than > don't manage>". When I watch htop as numpy.test() executes, sure