From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: GC improvements
Date: Wed, 04 Jan 2006 17:18:22 +0100 [thread overview]
Message-ID: <87oe2snf01.fsf@laas.fr> (raw)
In-Reply-To: <43BB1EDF.7080404@xs4all.nl> (Han-Wen Nienhuys's message of "Wed, 04 Jan 2006 02:03:27 +0100")
Hi Han-Wen,
Thanks for your input!
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> the easiest way is to modify
>
> scm_gc_for_newcell()
>
>
> so it directly passes to the
>
> scm_i_get_new_heap_segment (freelist, abort_on_error);
>
> case
No, that won't have any impact because this very case is rarely
reached.
I checked this by adding two (static) counters to `scm_gc_for_newcell ()':
one that counts the number of calls, and one that counts the number of
non-EOL returns of the first `scm_i_sweep_some_segments ()' call. The
ratio (still for the same workload) is _always_ very, very close to 1.
This is because `scm_i_sweep_some_segments ()' does not actually only
sweep segments: it sometimes (actually here, most of the time)
*initializes* them. The reason is that it uses `scm_i_sweep_some_cards ()'
which in turn chooses whether to initialize or sweep depending on
whether the segment at hand is already initialized (SWEEPER is chosen
based on SEG->FIRST_TIME).
This interleaving of initialization and sweeping makes it pretty hard to
track exactly where fresh cells come from. I guess one solution might
be to maintain a list of the uninitialized segments and pick cells
directly from there before actually sweeping.
To be continued... Hopefully! ;-)
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-01-04 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 16:32 GC improvements Ludovic Courtès
2005-12-23 11:29 ` Han-Wen Nienhuys
2005-12-23 15:40 ` 1.8 [was: GC improvements] Andy Wingo
2005-12-24 0:59 ` 1.8 Kevin Ryde
2006-01-03 10:16 ` GC improvements Ludovic Courtès
2006-01-04 1:03 ` Han-Wen Nienhuys
2006-01-04 16:18 ` Ludovic Courtès [this message]
2006-01-05 14:47 ` Ludovic Courtès
2006-01-06 20:22 ` Han-Wen Nienhuys
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=87oe2snf01.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-devel@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).