From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: guile-user@gnu.org
Subject: Re: "Pace is nothing without guile"
Date: Tue, 15 Jul 2008 21:21:56 +0200 [thread overview]
Message-ID: <87ej5v9cmj.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620807131006m4efc2a96v2d9778b6c4a501b4@mail.gmail.com
Hi,
"Neil Jerram" <neiljerram@googlemail.com> writes:
> So this email is about systematic performance data. I was wondering
> what benchmarks we could run to get good coverage of all Guile's
> function, and suddenly thought "of course, the test suite!"
Like Greg, I'm a bit suspicious about using the test suite as a
collection of micro-benchmarks. Usually, micro-benchmarks aim to assess
the cost of a specific operation, which must consequently be isolated to
avoid interference with unrelated computations.
Conversely, unit tests aim to verify that certain invariants hold,
regardless of "peripheral" computations required for that verification.
For instance, a few SRFI-14 tests use `every', a few SRFI-69 tests use
`lset=', various tests use `memq', etc. (OTOH, looking at the test
suite, I'm not sure whether these tests are exceptions.)
Other than that, my feeling is that it may be harder to analyze timings
of tests that were not written as micro-benchmarks in the first place,
since one must first determine what the test actually measures.
> - anyone running the tests and uploading data, not just Guile core developers
Although quite in fashion these days (see CDash), I'm not sure we
absolutely need such a tool. Having *some* benchmark suite to run seems
more important as a first step. :-)
Thanks,
Ludo'.
prev parent reply other threads:[~2008-07-15 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 17:06 "Pace is nothing without guile" Neil Jerram
2008-07-13 18:24 ` Greg Troxel
2008-07-13 22:31 ` Neil Jerram
2008-07-15 19:21 ` Ludovic Courtès [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=87ej5v9cmj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).