On Wed, 3 Nov 2004 12:52:26 -0800 (PST), Joshua Gatcomb
<[EMAIL PROTECTED]> wrote:
[snip]
> What we would like to do is determine if what we have
> done so far is sufficient or, if not, what specifically
> people would like to see.  Some of our unimplemented
> ideas so far are:
> 1.  Include the computed goto core
> 2.  Summary of results over N week(s)/month(s)
> 3.  Provide user form for dynamic results
>     If people would like this, they also need to
>     indicate what the form should provide:
>     (benchmark name, date, executable, etc)
> 4.  Provide HTML table of data for some/all of graphs
> 5.  Provide links for people to work locally
>     A.  A db schema/structure dump so people can
>         collect statistics on other architectures
>     B.  Source code
>     C.  daily db dump
> 
> If you would like to see any of these ideas
> implemented, or you have some of your own - please
> respond to this on the list.
[snip]

I think this is a really great idea.  I made some picture graphs for
the register allocation stuff myself, and tried to evangelize the idea
a little, but you guys have introduced a useful tool that can help
developers see the results of their work.  Now, one can anxiously
check the results after a checkin and see if a desired speedup has
occurred or not.  Great job.

To make this idea, and philosophy, pay off, we need (3&5B)++.  I think
what you're suggesting is to provide the software to others, so they
can run their own tests.  That's great, but I'd rather create the
test, check it in, and modify a master config file, that says which
tests will run.  The administrator, of course would have to approve
the patch.  For long tests, they don't have to be in the nightly test
suit, but could be run by name, by the user.

For number 4, I'd say that a comma separated values (CSV) file would
be most useful.  Then users can view and manipulate the data
themselves.  Various spreadsheets have nice capabilities for this, and
of course certain scripting languages can parse this kind of data
well.  So I hear, at least :).

Once again, great idea, great job!

~Bill

Reply via email to