unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
To: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Cc: 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: Sun, 3 Jun 2007 18:33:43 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706031822180.19138@iannis.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0706031646420.19138@iannis.localdomain>



On Sun, 3 Jun 2007, Kjetil Svalastog Matheussen wrote:

> 
> 
> (CC guile-dev)
> 
> 
> On Sun, 3 Jun 2007, Bill Schottstaedt wrote:
> 
> > Thanks!  I'll merge your changes into my versions this morning.
> > I saw some discussion about the Boehm GC, but I didn't try it --
> > let me know how it goes!
> > 
> 
> I have it running now, and it feels much better. (gc) still triggers a 
> glip in the sound though, but thats to be expected.
> 

I have tried Snd with Guile 1.9 with and without the Boehm GC on the same 
two computers (amd xp3000 and intel mac MP 1.3gz) using the same version 
of Snd (8.4/snd-ls 0.9.7.12). And my experiences are as follows:


> But the good things are (with snd_conffils.scm loaded):
> 
> * I don't hear any glips in the sound using a dac-size of 64. Can't 
>   remember that ever working before. Even a dac-size of 1 almost works.
> 

This is the same behaviour for both versions of guile. On the MP machine, 
there is never any glips at all, on the other there are some.


> * When changing the range, there is no sign of the graphics now and then 
>   lagging behind. I have never seen that before.
> 

Large difference. Without the Boehm GC, graphic freezes for about 0.5 
seconds each 4th seconds. Very frustrating, just as with guile 1.8.1, but 
better than 1.6.x though. With the Boehm GC, on the other hand: no freeze 
at all.

Conclusion: Guile with the Boehm GC seems to improve interactivety for 
one guile programs by a large amount, somehow. It would be nice if
the Boehm GC was used in guile 1.8 as well, and enabled by default.



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


  reply	other threads:[~2007-06-03 16:33 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 [this message]
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
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.0706031822180.19138@iannis.localdomain \
    --to=k.s.matheussen@notam02.no \
    --cc=bil@ccrma.Stanford.EDU \
    --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).