I am glad to announce that now you can see benchmark timing plots for multiple branches, thus being able to spot regressions in maintenance branches and compare enhancements in relation to previous releases.
e.g. * improving upon 1.7.x but still lacking behind 1.6.x http://www.onerussian.com/tmp/numpy-vbench/vb_vb_core.html#numpy-identity-100 http://www.onerussian.com/tmp/numpy-vbench/vb_vb_function_base.html#percentile ... * what seems to be a regression caught/fixed in 1.7.x: http://www.onerussian.com/tmp/numpy-vbench/vb_vb_indexing.html#a-indexes-float32 * or not (yet) fixed in 1.7.x http://www.onerussian.com/tmp/numpy-vbench/vb_vb_io.html#strided-assign-complex64 summary table generation is not yet adjusted for this multi-branch changes, so there might be misleading results there: http://www.onerussian.com/tmp/numpy-vbench/index.html#benchmarks-performance-analysis Cheers, -- 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 [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
