From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: our benchmark-suite
Date: Wed, 16 May 2012 19:01:49 +0200 [thread overview]
Message-ID: <8762bwhxfm.fsf@pobox.com> (raw)
In-Reply-To: <874ns77dh6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 25 Apr 2012 22:39:33 +0200")
Howdy!
On Wed 25 Apr 2012 22:39, ludo@gnu.org (Ludovic Courtès) writes:
>> So, those are the problems: benchmarks running for inappropriate,
>> inconsistent durations;
>
> I don’t really see such a problem. It doesn’t matter to me if
> ‘arithmetic.bm’ takes 2mn while ‘vlists.bm’ takes 40s, since I’m not
> comparing them.
Running a benchmark for 2 minutes is not harmful to the results, but it
is a bit needless. One second is enough.
However, running a benchmark for just a few milliseconds is not very
interesting:
;; ("if.bm: if-<bool>-then: executing then" 330000 real 0.011994627 real/iteration 3.63473545454545e-8 run/iteration 3.62829060606061e-8 core/iteration 9.61427360606058e-10 gc 0.0)
That's 12 milliseconds. The jitter there is too much.
>> inappropriate benchmarks;
>
> I agree that things like ‘if.bm’ are not very relevant now. But there
> are also appropriate benchmarks, and benchmarks are always better than
> wild guess. ;-)
Agreed :-)
>> and benchmarks being optimized out.
>
> That should be fixed.
In what way? It would make those benchmarks different.
Thesis: anything for which you would want to turn off the optimizer is
not a good benchmark anyway.
See also: http://www.azulsystems.com/presentations/art-of-java-benchmarking
>> My proposal is to rebase the iteration count in 0-reference.bm to run
>> for 0.5s on some modern machine, and adjust all benchmarks to match,
>> removing those benchmarks that do not measure anything useful.
>
> Sounds good. However, adjusting iteration counts of the benchmarks
> themselves should be done rarely, as it breaks performance tracking like
> <http://ossau.homelinux.net/~neil/bm_master_i.html>.
I think we've established that this isn't the case -- modulo the effect
that such a change would have on GC (process image size, etc)
>> Finally we should perhaps enable automatic scaling of the iteration
>> count. What do folks think about that?
>>
>> On the positive side, all of our benchmarks are very clear that they are
>> a time per number of iterations, and so this change should not affect
>> users that measure time per iteration.
>
> If the reported time is divided by the global iteration count, then
> automatic scaling of the global iteration count would be good, yes.
OK, will do.
Speak now or be surprised by a commit!
;-)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-05-16 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 9:22 our benchmark-suite Andy Wingo
2012-04-24 8:26 ` Andy Wingo
2012-04-25 20:39 ` Ludovic Courtès
2012-04-28 21:09 ` Neil Jerram
2012-05-02 21:24 ` Ludovic Courtès
2012-05-04 21:43 ` Neil Jerram
2012-05-07 14:38 ` Ludovic Courtès
2012-05-15 20:48 ` Andy Wingo
2012-05-19 21:54 ` Neil Jerram
2012-05-16 17:01 ` Andy Wingo [this message]
2012-05-16 21:01 ` Ludovic Courtès
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=8762bwhxfm.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).