From: Miroslav Silovic <miro@puremagic.com>
Cc: guile-devel@gnu.org, jantien@xs4all.nl
Subject: Re: GUILE GC -- Write barrier for vectors
Date: Mon, 15 Jul 2002 12:56:28 +0200 [thread overview]
Message-ID: <3D32AA5C.90600@puremagic.com> (raw)
In-Reply-To: 15665.63423.468913.715296@blauw.xs4all.nl
hanwen@cs.uu.nl wrote:
>Linked against 1.7.0 without-threads, lily uses approximately 20% of
>its time in GC on a 400 mhz PII/SDRAM. In another instance, the same
>compile with lilypond linked against 1.5.6 on a 1Ghz PIII/DDR RDRAM,
>uses approximately 50% of the total running time (!) for GC'ing.
>
>Can anyone comment on the difference in running times? I didn't see
>much in the changelog that could explain this difference. Could it be
>that there is some anomaly that causes the timings to be skewed on the
>fast machine? The total speed increase going from the 400mhz machine
>to the 1ghz is consistent with the clock freqs.
>
>Can anyone comment on how to improve the performance?
>
>
I had a similar problem when working with a large number of vector-like
things - basilly
my application would trigger GC more often than necessary. The reason
was that I didn't
properly report bytes allocated to Guile (i.e. my use of scm_must_malloc
was broken).
If you're reporting too much, the GC will trigger all the time.
Alternatively, if you're reporting
more alloc than freed bytes, you'll get bytes counter mismatch (VERY
similar to memory leak),
and this will completely confuse GC scheduler.
Miro
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-15 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 22:14 GUILE GC -- Write barrier for vectors hanwen
2002-07-15 10:56 ` Miroslav Silovic [this message]
2002-07-15 11:00 ` Han-Wen Nienhuys
2002-07-15 11:36 ` Miroslav Silovic
2002-07-15 16:49 ` Dirk Herrmann
2002-07-15 18:22 ` Han-Wen Nienhuys
2002-07-15 20:07 ` Dirk Herrmann
2002-07-15 23:02 ` Han-Wen
2002-07-16 9:22 ` Han-Wen Nienhuys
2002-07-16 23:04 ` Dirk Herrmann
2002-07-16 23:26 ` Han-Wen
2002-07-17 21:53 ` Han-Wen
2002-07-19 23:48 ` Dirk Herrmann
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=3D32AA5C.90600@puremagic.com \
--to=miro@puremagic.com \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).