Comments on: Visualising our Labours http://www.oxymoronical.com/blog/2008/02/Visualising-our-Labours Spouting nonsense from the depths of my spare time Tue, 02 Mar 2010 15:42:15 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Justin Dolske http://www.oxymoronical.com/blog/2008/02/Visualising-our-Labours#comment-28 Justin Dolske Tue, 05 Feb 2008 21:36:20 +0000 http://www.oxymoronical.com/blog/2008/02/Visualising-our-Labours#comment-28 I think that even though the timeplot would be better with more perf runs, something like that would still be very helpful. As it is now, it's a pain to correlate changes in the graphs to specific checkins. An easy (and *reliable*!) way to know what checkins caused a number to change would be helpful in tracking down regressions, and casual "did my checkin regress anything" browsing.<br> <br> Huge +1 to cleanun up Tinderbox too. I've been thinking that all the perf numbers should just be removed, in favor of graphical views (like the perf dashboard). Maybe show serious regressions ("Tp went up 40% in this build"), but that would be a fair amount of work, and a highly-usable set of graphs would show the same info anyway. I think that even though the timeplot would be better with more perf runs, something like that would still be very helpful. As it is now, it’s a pain to correlate changes in the graphs to specific checkins. An easy (and *reliable*!) way to know what checkins caused a number to change would be helpful in tracking down regressions, and casual "did my checkin regress anything" browsing.

Huge +1 to cleanun up Tinderbox too. I’ve been thinking that all the perf numbers should just be removed, in favor of graphical views (like the perf dashboard). Maybe show serious regressions ("Tp went up 40% in this build"), but that would be a fair amount of work, and a highly-usable set of graphs would show the same info anyway.

]]>