From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: "Ludovic Courtès" <ludovic.courtes@laas.fr>
Cc: Bill Schottstaedt <bil@ccrma.Stanford.EDU>,
guile-devel@gnu.org,
Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
Subject: Re: Experience with guile + Boehm GC in SND (Re: New versions of rt-compiler.scm, rt-examples.scm and rt.tex
Date: Mon, 4 Jun 2007 14:08:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706041353330.9033@ttleush> (raw)
In-Reply-To: <87zm3gq77r.fsf@laas.fr>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2099 bytes --]
On Mon, 4 Jun 2007, Ludovic Courtès wrote:
> Hi,
>
> Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no> writes:
>
>> [2] tla my-default-archive lcourtes@laas.fr--2006-libre
>> tla get guile-core--boehm-gc
>
> So that's the one you've been using and referring to as "Guile + Boehm
> GC"? Glad to hear it! ;-)
>
Sorry I didn't write that in my first mail.
> Did you make sure to compile libgc "the right way", so that locking in
> with a multi-threaded libgc doesn't hurt performance[0]?
>
I have tried with and without both --enable-threads=posix
and --enable-parallel-mark. No difference, it seems to work perfectly
anyway.
> The main thing that needs to be done before we can consider this
> solution now is to compare both memory usage _and_ execution time of the
> two Guiles.
Yes, but for some kinds of software, like programs with custom gui's,
sound processing programs, interactive graphical programs, interactivety
is exclusively more important than those two. I consider the freeze that
the guile's built-in gc cause to be its biggest problem.
In fact, I don't think execution time is an important factor here at all.
Don't get me wrong, of course execution time is important in general, but
a change in execution time of a gc benchmark program within the factor of
two sounds like an insignificant difference compared to what is gained in
interactivity.
> For instance, with the default settings, Guile + Boehm GC is slightly
> faster than Guile when running `gcbench.scm', but it might consume more
> memory. This needs to be analyzed. Reports as to how this impacts SND
> are also more than welcome, of course! ;-)
>
I'm going to run Guile + Boehm GC + SND for a while now and report back if
anything unusual happens. I might even release a special version of SND
with guile + the Boehm GC included to the public in the near future,
because of the huge advantages it has. This might generate a lot of
feedback. And if no one reports back, then its a good sign that it works
well.
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-06-04 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0706031204540.9006@ttleush>
[not found] ` <20070603110930.M29119@ccrma.Stanford.EDU>
2007-06-03 14:57 ` Experience with guile + Boehm GC in SND (Re: New versions of rt-compiler.scm, rt-examples.scm and rt.tex Kjetil Svalastog Matheussen
2007-06-03 16:33 ` Kjetil Svalastog Matheussen
2007-06-03 20:07 ` Kjetil Svalastog Matheussen
2007-06-04 11:39 ` Ludovic Courtès
2007-06-04 12:08 ` Kjetil S. Matheussen [this message]
2007-06-04 12:45 ` Kjetil S. Matheussen
2007-06-04 13:22 ` Ludovic Courtès
2007-06-04 16:11 ` Kjetil S. Matheussen
2007-06-04 16:50 ` Ludovic Courtès
2007-06-04 18:00 ` Kjetil S. Matheussen
2007-06-04 18:14 ` Kjetil S. Matheussen
2007-06-05 7:53 ` 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=Pine.LNX.4.64.0706041353330.9033@ttleush \
--to=k.s.matheussen@notam02.no \
--cc=bil@ccrma.Stanford.EDU \
--cc=guile-devel@gnu.org \
--cc=ludovic.courtes@laas.fr \
/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).