From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Introspective benchmarking.
Date: Wed, 03 Apr 2002 01:01:20 -0800 [thread overview]
Message-ID: <E16sgds-0002ct-00@giblet> (raw)
In-Reply-To: <87pu1zucdi.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Tue, 19 Mar 2002 21:49:45 -0600)
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
prev parent reply other threads:[~2002-04-03 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 3:49 Introspective benchmarking Rob Browning
2002-04-03 9:01 ` Thien-Thi Nguyen [this message]
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=E16sgds-0002ct-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).