unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Benchmark tracking
Date: Sun, 08 Nov 2009 21:35:43 +0000	[thread overview]
Message-ID: <87zl6wya1c.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87r5s8zvkm.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 08 Nov 2009 20:05:13 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Neil,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>>   http://ossau.homelinux.net/~neil/
>
> This looks really good to me.  The only thing that’s missing is a
> mapping from units on the X axis to commits.

That's at http://ossau.homelinux.net/~neil/bm_master_x.html, and it
is linked from the main page above.

> Looking at http://ossau.homelinux.net/~neil/bm_master_i.html, it seems
> that several things got slightly slower around x = 25.

x = 25 => early morning of 2009-10-23, commit
04c68c039194f33d5bd7e8b1f21eba7c8bd6adbe.

I agree that many tests made a bit of a jump then, but remember that
that could be caused just by something unusual happening on my build
machine.  I'm not aware of anything unusual on that date... but it's
still possible.

Also, in many cases the loss seems to have been recovered again since
then.

And, looking at the commits on 2009-10-22:

	Compile Guile modules with `-Wunbound-variable'.

	Fix typos leading to unbound variable references.

	Adjust `unbound-variable' GOOPS heuristic for `goops... 

	Fix bytecode disassembler.

	SRFI-88: Call `read-set!' at compile time and run time.

None of these look like they could have caused a slow down.

I'm not sure we can rely very much on these graphs for day-to-day
changes, because I haven't eliminated all possible external factors, so
there is considerable random variation.  I'd say their value is more to
give us confidence that we don't slow Guile down over the medium term.

Regards,
      Neil




  reply	other threads:[~2009-11-08 21:35 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
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 [this message]
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=87zl6wya1c.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).