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.
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 so they are not present in the summary table.
could well be related to 80% faster det()? ;)
norm was hit as well a bit earlier, might well be within these commits:
https://github.com/numpy/numpy/compare/24a0aa5...29dcc54
I will rerun now benchmarking for the rest of commits (was running last
in the day iirc)
Cheers,
On Tue, 16 Jul 2013, Yaroslav Halchenko wrote:
> and to put so far reported findings into some kind of automated form,
> please welcome
> http://www.onerussian.com/tmp/numpy-vbench/#benchmarks-performance-analysis
> This is based on a simple 1-way anova of last 10 commits and some point
> in the past where 10 other commits had smallest timing and were significantly
> different from the last 10 commits.
> "Possible recent" is probably too noisy and not sure if useful -- it should
> point to a closest in time (to the latest commits) diff where a
> significant excursion from current performance was detected. So per se it has
> nothing to do with the initial detected performance hit, but in some cases
> seems still to reasonably locate commits hitting on performance.
> Enjoy,
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion