----- Original Message -----
From: "Graham Percival" <gra...@percival-music.ca>
To: "Nick Payne" <nick.pa...@internode.on.net>
Cc: "胡海鹏 - Hu Haipeng" <hhpmu...@163.com>; <lilypond-user@gnu.org>
Sent: Tuesday, February 15, 2011 1:56 AM
Subject: Re: can't compile
On 2/15/11, Nick Payne <nick.pa...@internode.on.net> wrote:
> On 15/02/11 09:28, ??? - Hu Haipeng wrote:
>> I'm almost near the end of my second work (still about 80-100 bars not
>> written). The day before yesterday, when I was at bar 362, Lily could
>> still compile it within 2 hours.
...
> I commented out the \midi { } in the score block and ran another
> compilation. When I checked after a few minutes, System Monitor showed
> that Lilypond was using 1.1Gb of RAM
That sounds like a lot. After 2.13.50, we added some optimizations.
If anybody sees the same behaviour from current git or 2.13.51, it
might be good to try constructing a Tiny example of the problem so
that programmers can investigate if it's a bug.
Cheers,
- Graham
Once the Windows version of 13.51 is available, I can benchmark memory usage
in comparison with 13.35 - I did a memory monitoring exercise on that using
my Mikado score.
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00257.html
--
Phil Holmes
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user