From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Benchmark tracking
Date: Wed, 28 Oct 2009 00:24:52 +0100 [thread overview]
Message-ID: <m3hbtkju7v.fsf@pobox.com> (raw)
In-Reply-To: <871vkoldwc.fsf@ossau.uklinux.net> (Neil Jerram's message of "Tue, 27 Oct 2009 21:34:27 +0000")
On Tue 27 Oct 2009 22:34, Neil Jerram <neil@ossau.uklinux.net> writes:
> I've been running benchmarks for a while in my overnight builds, and
> have put up a web page to show the results from that:
>
> http://ossau.homelinux.net/~neil/
Interesting!
> In summary, there's nothing to be concerned about (apart from a possible
> slight slowdown in the last week or so).
I think callee-parsed args did slow things down a bit. Would like to
figure out why, and at what exact commit.
Hm, would be good to bisect this more closely. Would it be possible to
map the X axis to commits?
Also, we should have more of the stock Gabriel benchmarks, like in the
Clinger or Feeley set.
> The real point of this email is just to mention this tracking - which
> I hope will help us notice if we introduce significant performance
> gains or losses in the future.
Great!
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-10-27 23:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 21:34 Benchmark tracking Neil Jerram
2009-10-27 23:24 ` Andy Wingo [this message]
2009-10-30 23:26 ` Neil Jerram
2009-10-31 0:24 ` Mike Gran
2009-10-31 22:06 ` Neil Jerram
2009-11-08 19:11 ` Ludovic Courtès
2009-11-08 21:50 ` Andy Wingo
2009-11-04 22:03 ` Neil Jerram
2009-11-04 23:34 ` Neil Jerram
2009-11-08 18:59 ` Ludovic Courtès
2009-10-28 8:54 ` Ludovic Courtès
2009-10-31 23:01 ` Neil Jerram
2009-11-04 21:10 ` Neil Jerram
2009-11-08 19:05 ` Ludovic Courtès
2009-11-08 21:35 ` Neil Jerram
2009-11-08 22:50 ` 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=m3hbtkju7v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).