From: Neil Jerram <neil@ossau.uklinux.net>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: freeing srcprops ?
Date: Sun, 28 Jan 2007 09:08:52 +0000 [thread overview]
Message-ID: <87hcub4ixn.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87k5zjapmp.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 19 Jan 2007 10:20:30 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>>
>> why use a separate storage pool for srcprop objects?
>
> At a guess, is it because that they're likely to never need freeing,
> hence can be laid down in big blocks.
I'd guess because setting up a srcprops is critical to start-up
performance, and a double cell doesn't have enough slots to store all
the common properties (filename, pos, copy) directly (as your change
makes clear).
So I'd expect --debug start up to go a little more slowly after your
change. Did you make any measurements?
Also, did you find that the change saved a lot of memory for Lilypond?
It's not obvious to me why it should have done, just moving srcprops
from a specialized storage to the general cell heap.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-28 9:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 0:22 freeing srcprops ? Han-Wen Nienhuys
2007-01-18 14:04 ` Han-Wen Nienhuys
2007-01-18 23:28 ` Kevin Ryde
2007-01-19 10:37 ` Han-Wen Nienhuys
2007-01-19 11:52 ` Han-Wen Nienhuys
2007-01-26 22:15 ` Kevin Ryde
2007-01-26 23:33 ` Han-Wen Nienhuys
2007-01-18 23:20 ` Kevin Ryde
2007-01-28 9:08 ` Neil Jerram [this message]
2007-01-29 11:39 ` Han-Wen Nienhuys
2007-01-29 21:35 ` Neil Jerram
2007-01-29 23:31 ` Han-Wen Nienhuys
2007-01-30 12:40 ` Ludovic Courtès
2007-01-30 19:14 ` Han-Wen Nienhuys
2007-01-30 12:21 ` Mikael Djurfeldt
2007-01-30 12:52 ` Han-Wen Nienhuys
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=87hcub4ixn.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).