Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-23 Thread Nathaniel Smith
The biggest ~recent change in master's linalg was the switch to gufunc back ends - you might want to check for that event in your commit log. On 19 Jul 2013 23:08, Yaroslav Halchenko li...@onerussian.com wrote: I have just added a few more benchmarks, and here they come

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-23 Thread Yaroslav Halchenko
On Mon, 22 Jul 2013, Benjamin Root wrote: At some point I hope to tune up the report with an option of viewing the plot using e.g. nvd3 JS so it could be easier to pin point/analyze interactively. shameless plug... the soon-to-be-finalized matplotlib-1.3 has a WebAgg

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-23 Thread Benjamin Root
On Mon, Jul 22, 2013 at 1:28 PM, Yaroslav Halchenko li...@onerussian.comwrote: On Mon, 22 Jul 2013, Benjamin Root wrote: At some point I hope to tune up the report with an option of viewing the plot using e.g. nvd3 JS so it could be easier to pin point/analyze

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-22 Thread Yaroslav Halchenko
On Fri, 19 Jul 2013, Warren Weckesser wrote: Well, this is embarrassing: https://github.com/numpy/numpy/pull/3539 Thanks for benchmarks! I'm now an even bigger fan. :) Great to see that those came of help! I thought to provide a detailed details (benchmarking all recent commits) to provide

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-22 Thread Benjamin Root
On Mon, Jul 22, 2013 at 10:55 AM, Yaroslav Halchenko li...@onerussian.comwrote: At some point I hope to tune up the report with an option of viewing the plot using e.g. nvd3 JS so it could be easier to pin point/analyze interactively. shameless plug... the soon-to-be-finalized matplotlib-1.3

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-20 Thread Pauli Virtanen
20.07.2013 01:38, Nathaniel Smith kirjoitti: The biggest ~recent change in master's linalg was the switch to gufunc back ends - you might want to check for that event in your commit log. That was in mid-April, which doesn't match with the location of the uptick in the graph. Pauli

Re: [Numpy-discussion] fresh performance hits: numpy.linalg.pinv 30% slowdown

2013-07-19 Thread Warren Weckesser
On 7/19/13, Yaroslav Halchenko li...@onerussian.com wrote: I have just added a few more benchmarks, and here they come http://www.onerussian.com/tmp/numpy-vbench/vb_vb_linalg.html#numpy-linalg-pinv-a-float32 it seems to be very recent so my only check based on 10 commits didn't pick it up yet