2007/5/4, Nicolas Sceaux <[EMAIL PROTECTED]>:
Joe Neeman <[EMAIL PROTECTED]> writes:> I recently discovered that the new page-breaking algorithm is slow when there > are many small scores. As a workaround, put > \paper { > #(define page-breaking optimal-page-breaks) > } > at the top of the file. I've recently faced the case where the page breaker (or so it seems) actually does not finish its job. That was with a ~100-score book, on a machine with 3Gbytes of RAM, with LilyPond 2.11.23. After the last "Preprocessing graphical objects...", the lilypond process uses ~1Gbyte of memory, then slowly increases up to using all the memory available, wthout finishing.
There have been some reports that somewhere in the recent 2.11 versions, the memory use has regressed. This is probably not related to Page breaking. I'll have a look over the weekend to see if I can see anything. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
