From: Rob Browning <rlb@defaultvalue.org>
Subject: Introspective benchmarking.
Date: Tue, 19 Mar 2002 21:49:45 -0600 [thread overview]
Message-ID: <87pu1zucdi.fsf@raven.i.defaultvalue.org> (raw)
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
next reply other threads:[~2002-03-20 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 3:49 Rob Browning [this message]
2002-04-03 9:01 ` Introspective benchmarking Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pu1zucdi.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).