There are some attempts to optimize the speed; one simple patch reduces the time required by something like 40%. But you should expect such problems from an unstable development version.
Cheers, - Graham On Thu, Jul 15, 2010 at 06:22:56PM +0800, 胡海鹏 - Hu Haipeng wrote: > Hello, > I finally finish my concert overture, which has just 250 measures, 34 > pages. The compiling is a nightmare! When I used normal way, the computer > turned into a circumstance like it was about to crash. Then I used Process > Tamer, a small util program to reduce source wasting. At first, it's ok to > do anything while compiling, but after 5 minutes, the computer again > became very slow. Then I went away to listen to The Firebird. After its 45 > minutes' music, Lilypond was still compiling. I checked the task manager, > and found it first used around 120M of RAM, but then continuous ascend to > over 520M, and then fall to 330M, and up to 472... After another about 50 > minutes, The score was at last ready. The whole process took about 110 > minutes!!! I'd like to know why Lilypond should use such a large memory, > since cpu is not taken too much (but instead, "system idle process.exe" > took very large percent (up to 94%) of cpu). I think I must buy a Win7 > machine with 4 core cpu and 8gb RAM, otherwise I can't write a piece like > The Firebird, which will burn my current machine into dust :-) > Regards > Haipeng > > ---------------------------------------------------------------------- > > A:uIeOuOD--oIIo/O *Aa.NOEIa:O>>NuC,?'ouA:Ei 1/4thAd--L-? > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
