From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: GC brokenness in `master'
Date: Wed, 11 Mar 2009 00:08:14 +0000 [thread overview]
Message-ID: <87r614diq9.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <877i2x7x6l.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Wed\, 11 Mar 2009 00\:52\:34 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> ("subr.bm: subr invocation: simple subr" 700000 total 0.98)
>> ("subr.bm: subr invocation: generic subr" 700000 total 1.39)
>> ("subr.bm: subr invocation: generic subr with rest arg" 700000 total 1.32)
>> ("subr.bm: subr invocation: generic subr with rest arg and 3+ parameters" 700000 total 1.63)
>
> "Interestingly", this is roughly twice as slow as 1.8 (!).
>
> After some manual bisecting, I found the offending commit (dated
> 2008-08-16):
>
> http://git.savannah.gnu.org/cgit/guile.git/commit/?id=82ae1b8eb3413e6be6bd2aa032986fc7782e85ac
But presumably this doesn't matter much, if we are going to switch to
BDW-GC. What's your latest thinking on that?
> Strangely enough, the "simple subr" case, which is not GC-intensive, is
> slower with BDW-GC. This needs further investigation...
It's not very much slower - and IMO, not serious enough to be a
significant factor against BDW-GC.
But it's nicer to understand things fully, so I agree that
investigation would be good too.
Neil
next prev parent reply other threads:[~2009-03-11 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 0:22 Putting an end to "compiled closures" Ludovic Courtès
2009-02-23 22:10 ` Ludovic Courtès
2009-03-01 23:34 ` Ludovic Courtès
2009-03-08 16:18 ` Ludovic Courtès
2009-03-10 23:52 ` GC brokenness in `master' Ludovic Courtès
2009-03-11 0:08 ` Neil Jerram [this message]
2009-03-11 9:23 ` 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=87r614diq9.fsf@arudy.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).