unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-devel@gnu.org
Subject: Re: lazy sweeping.
Date: Mon, 29 Jul 2002 15:16:59 +0200	[thread overview]
Message-ID: <3D45404B.4010706@nada.kth.se> (raw)
In-Reply-To: 15684.32520.154258.348830@blauw.xs4all.nl

Han-Wen wrote:

>Here are some results of my lazy sweeping implementation:
>
>[...]
>
>The lazy sweeping approximately halves the startup time of GUILE. I
>consider the old GC beat; when can we start integrating this? 
>
Nice! However, be careful about benchmarking information. When hacking
the evaluator, I've noticed performance changes up to 30% just by changing
the textual order of functions within a compilation unit...

> * Lazy sweeping naturally complements multi-threaded use: whenever a
>   thread runs out of free cells, we can simply sweep a few (say 512)
>   cells, and return that for private use by that thread.
>
[Without having studied your code:] Is it enough to lock one mutex for the
joint apparatus of sweeping and marking before doing the lazy sweep
in order to avoid interference between threads?  (One would not want to
stop all threads before sweeping 512 cells...)

Best,
M




_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-07-29 13:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 23:32 lazy sweeping Han-Wen
2002-07-29  0:07 ` Michael Livshin
2002-07-29  9:48   ` Han-Wen Nienhuys
2002-07-29 10:14     ` Michael Livshin
2002-07-29 12:40       ` Han-Wen Nienhuys
2002-07-29 13:00         ` Michael Livshin
2002-07-29 13:06           ` Han-Wen Nienhuys
2002-07-30 10:09   ` Han-Wen
2002-07-30 12:10     ` Michael Livshin
2002-07-29  4:31 ` Tom Lord
2002-07-29 15:17   ` Han-Wen Nienhuys
2002-07-29 13:16 ` Mikael Djurfeldt [this message]
2002-07-29 13: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=3D45404B.4010706@nada.kth.se \
    --to=djurfeldt@nada.kth.se \
    --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).