From: "Ludovic Courtès" <ludo@gnu.org>
To: Han-Wen Nienhuys <hanwenn@gmail.com>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: garbage collection slowdown
Date: Wed, 05 Feb 2020 17:22:55 +0100 [thread overview]
Message-ID: <877e11m2ao.fsf@gnu.org> (raw)
In-Reply-To: <CAOw_e7aDrRZ9_zhh5_P7BqsXAeHvRNoQSAJRnpTF_Rg7nsUkQw@mail.gmail.com> (Han-Wen Nienhuys's message of "Sat, 1 Feb 2020 10:34:32 +0100")
Hi Han-Wen,
Great to see you back here!
Han-Wen Nienhuys <hanwenn@gmail.com> skribis:
> On Tue, Jan 28, 2020 at 11:41 PM Han-Wen Nienhuys <hanwenn@gmail.com> wrote:
>> Unfortunately, it looks like the adoption of the BDW GC library caused
>> a ~6x slowdown, causing an overall end-to-end slowdown of 50%.
>>
>> I was wondering if you folks would have tips to further tune GC for
>> wall-time speed, and if there additional diagnostics to see if we're
>> doing something extraordinarily silly.
>
> For the record, I managed to solve this, by scaling up the heap more
> aggressively. See
> https://codereview.appspot.com/561390043/diff/557260051/lily/score-engraver.cc
Weird. It would be interesting to see where the slowdown comes from.
Overall, my recollection of the 1.8 to 2.0 transition (where we
introduced libgc) is that GC was a bit faster, definitely not slower.
That said, does LilyPond happen to use lots of bignums and/or lots of
finalizers? Finalizers, including those on bignums, end up being very
GC-intensive, as discussed in my recent message. Perhaps that’s what’s
happening here, for instance if you create lots of SMOBs with a free
function.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-02-05 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 22:41 garbage collection slowdown Han-Wen Nienhuys
2020-01-29 0:47 ` Arne Babenhauserheide
2020-01-29 7:17 ` Han-Wen Nienhuys
2020-02-01 9:34 ` Han-Wen Nienhuys
2020-02-05 16:22 ` Ludovic Courtès [this message]
2020-02-05 22:31 ` Han-Wen Nienhuys
2020-02-06 14:06 ` Mikael Djurfeldt
2020-02-06 17:19 ` 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=877e11m2ao.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=hanwenn@gmail.com \
/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).