unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
Cc: Bill Schottstaedt <bil@ccrma.Stanford.EDU>, guile-devel@gnu.org
Subject: Re: Experience with guile + Boehm GC in SND (Re: New versions of rt-compiler.scm, rt-examples.scm and rt.tex
Date: Mon, 04 Jun 2007 18:50:35 +0200	[thread overview]
Message-ID: <87vee3k6jo.fsf@laas.fr> (raw)
In-Reply-To: Pine.LNX.4.64.0706041759250.9033@ttleush

Hi,

"Kjetil S. Matheussen" <k.s.matheussen@notam02.no> writes:

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

So `THREAD_LOCAL_ALLOC' was defined in your libgc build, right?

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

"Directly in Guile" means that you just run:

  $ ./pre-inst-guile gcbench.scm

Is that correct?

> 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.

What does "inside snd" mean exactly?

Is snd multi-threaded?  Does it use `scm_without_guile ()' for instance
(e.g., when a thread blocks for I/O)?

Does the second run of `gcbench.scm' within Guile alone (no snd) show
similar performance behavior in the libgc case?  I.e.:

  $ guile-boehm --no-debug
  guile> (load "gcbench.scm")
  ;;; takes 50s. to complete
  guile> (load "gcbench.scm")
  ;;; takes 118s. to complete


For libgc, there are a few environment variables that might be
influential, e.g., `GC_MAXIMUM_HEAP_SIZE' (see `README.environment' from
libgc).  Likewise for Guile's GC, but they're undocumented AFAIK (grep
for `scm_getenv_int' in the `libguile' directory).

Thanks,
Ludovic.


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


  reply	other threads:[~2007-06-04 16:50 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
2007-06-04 16:50                 ` Ludovic Courtès [this message]
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=87vee3k6jo.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=bil@ccrma.Stanford.EDU \
    --cc=guile-devel@gnu.org \
    --cc=k.s.matheussen@notam02.no \
    /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).