unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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 S. 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 18:11:01 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706041759250.9033@ttleush> (raw)
In-Reply-To: <87d50bq2gz.fsf@laas.fr>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1337 bytes --]



On Mon, 4 Jun 2007, Ludovic Courtès wrote:

>> Actually, I haven't used guile for other interactive stuff than
>> snd. And snd is huge. It could be that the boehm gc works a lot lot
>> better for really large programs than guile's gc. I'll try to run the
>> gc benchmark program inside snd (with lots of scheme files loaded), it
>> might give some interesting results.
>
> Cool, let us know how it goes.
>

I used the gc benchmark program posted by Han-Wen:
http://www.mail-archive.com/guile-devel@gnu.org/msg01077.html

libgc (v6.8) was compiled with the --enable-threads=posix only.

For normal guile I used 1.8.1, default gentoo build. (-O2)
For GC guile, I built from your tree. (also -O2)

Snd is snd-ls V0.9.7.12.

My machine is an XP2800, single processor.


Running the benchmark program directly in guile gives no difference. Both 
spent about 50 seconds running the test.

Inside snd is another matter:


           [1]   [2]      [3]
Guile gc  96mb  176mb    54s.
Boehm gc  99mb  107mb   118s.


[1] Memory before running test reported by top.
[2] Memory after running test reported by top
[3] Time to run test in seconds.

All tests performed twice to ensure nothing special happened in one of 
them. The numbers here are from last test, and are about the same as 
from the run.

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

  reply	other threads:[~2007-06-04 16:11 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
2007-06-04 12:45             ` Kjetil S. Matheussen
2007-06-04 13:22             ` Ludovic Courtès
2007-06-04 16:11               ` Kjetil S. Matheussen [this message]
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.0706041759250.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).