> At 11:08 PM -0800 11/2/04, Jeff Clites wrote:
> >On Nov 2, 2004, at 7:10 PM, Matt Diephouse wrote:
> >
> >>Joshua Gatcomb and I have been working a little
> under a week to set up
> >>an automated build system for parrot that tracks
> performance (with
> >>help from Dan's box). We have collected benchmark
> data for regular and
> >>optimized builds with and without JIT from June
> 1st through October.
> >>
> >>With some help from Perl and GD, we've up several
> pages of graphs:
> >>
> >> http://www.sidhe.org/~timeparrot/graphs/
> >>
> >>Both the build process and the creation of the
> graphs will (hopefully)
> >>be run daily (automated). There are plans to do
> some other things with
> >>the data as well (some notification scripts).
> >
> >Very cool. A useful thing to do would be to
> preserve all of the
> >builds, so that newly-created benchmarks could be
> back-filled. (That
> >way, if we realize that we've not been effectively
> testing
> >something, we can devise an appropriate benchmark,
> and evaluate the
> >consequences of past design changes against it.)
>
Actually, we already thought of that. We were
thinking more along the lines of people wanting to
check other run-time cores (such as computed goto).
To save on disk space, the executables are stripped
and bzip2'd, but we can go back easily to any previous
point in the 5 month window if we want.
Cheers
Joshua Gatcomb
a.k.a. Limbic~Region
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
