From: Han-Wen <hanwen@cs.uu.nl>
Subject: scm_register_collectable_memory() ?
Date: Sat, 3 Aug 2002 20:20:33 +0200 [thread overview]
Message-ID: <15692.7921.99684.944726@blauw.xs4all.nl> (raw)
Hi,
Question: why does GUILE do a GC when a lot of memory malloced memory
is used? I understand that doing GC frees up some of that memory, but
every piece of collectable malloc memory is already connected with a
cell, and we do GC for those regularly (i.e. when we run out of
cells.)
For example, the doc snarfer, which is quite heavy with malloced stuff
(strings), does many times more often malloc triggered GCs, and most
the of the yields are low. Why don't we measure yields, and adjust the
triggers, similar to how cells are done?
Precise numbers:
58 gcs, of which 47 are induced by scm_register_collectable_memory().
Average yield (i.e (mallocedbefore - mallocedafter) / mallocedbefore )
of 14 %. This is for the snarf-check-and-output-texi script, run on
the GUILE sources.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2002-08-03 18:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15692.7921.99684.944726@blauw.xs4all.nl \
--to=hanwen@cs.uu.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).