Introspective benchmarking.

Introspective benchmarking.

[Rob Browning]

I feel like it would be extremely helpful to have a set of benchmarks
that we can run in order to help evaluate our changes.  While I'm well
aware of the risks involved in benchmarking, I think even a moderately
good set could provide a healthy sanity check of our efforts.

What I'm wondering is how the benchmarks should be handled.  For
example, I feel like they probably shouldn't be part of the main
(core) CVS tree, if for no other reason than not having to worry as
much about about copyright assignments.  There's also the argument
that they don't belong with any one tree since we should probably be
using them to test across guile versions.

I don't know how many people have ever looked, but stalin has a fairly
large set of benchmarks in ./benchmarks.  I've played around a bit and
found so far that many of the files will run just fine as-is, though
if we want to be able to run the tests in a reasonable amount of time
we'll need to lower a lot of the final looping constants by a couple
of orders of magnitude or so :/

Stalin's source tree can actually run the set of benchmarks across a
set of scheme implementations: bigloo, stalin, scheme->c, gambit-c,
and chez, but it takes about two days on a 450MHz Xeon...

Thoughts?

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Introspective benchmarking.

[Thien-Thi Nguyen]

   From: Rob Browning <rlb@defaultvalue.org>
   Date: Tue, 19 Mar 2002 21:49:45 -0600

   I feel like it would be extremely helpful to have a set of benchmarks
   that we can run in order to help evaluate our changes.  While I'm well
   aware of the risks involved in benchmarking, I think even a moderately
   good set could provide a healthy sanity check of our efforts.

yeah it's good to get that stuff in now (while guile is slow ;-).  it
should not be put in guile-core, that's for sure...  pick a sensible
place under workbook/ and go for it (twiddle TODO for the spider).

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel