From: lilydev@muurbloem.xs4all.nl (Han-Wen Nienhuys)
Subject: Re: Guile + Boehm GC
Date: Tue, 21 Mar 2006 17:44:20 +0000 (UTC) [thread overview]
Message-ID: <dvpe1j$3r5$1@sea.gmane.org> (raw)
In-Reply-To: 87r74vd858.fsf@laas.fr
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
In article <87r74vd858.fsf@laas.fr>,
Ludovic Courtès <ludovic.courtes@laas.fr> wrote:
>>
>> http://www.xs4all.nl/~hanwen/public/guile/guile-boehm.gz
>>
>> note that this is a patch for the "old" GC code, before I took a stab
>> at rewriting.
>
>The good news is that it looks quite simple! The main changes are
>located here (diffstat):
>
> libguile/gc.c | 854 +-----------------------------------------
> libguile/gc.h | 57 --
>
>However, it looks like you didn't look at weak hash tables back then.
>My impression is that porting them would be the most difficult task.
Yes, correct. It was a quick hack.
>> BTW, I ran across Judy trees today,
>>
>> http://judy.sourceforge.net/
>>
>> would it be worthwhile to try replacing resizing hash tables in Guile
>> with Judy trees? I expect that it would incur a significant speedup.
>
>I was not aware of this project but I'm not so sure it would have a
>significant impact. Currently, Guile spends a huge amount of time
>managing memory and improving this should be priority #1 I think.
Quite possibly, but LilyPond is my main application, and Lily also
spends a lot of time doing various kinds of hashtable lookups.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-03-21 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 14:05 Guile + Boehm GC Ludovic Courtès
2006-03-21 14:41 ` Nic
2006-03-21 15:29 ` Han-Wen Nienhuys
2006-03-21 17:23 ` Ludovic Courtès
2006-03-21 17:44 ` Han-Wen Nienhuys [this message]
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='dvpe1j$3r5$1@sea.gmane.org' \
--to=lilydev@muurbloem.xs4all.nl \
--cc=hanwen@lilypond.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).