[EMAIL PROTECTED] writes:
> > Another problem that is hard to solve quickly is that the
> > score takes 2 1/2 hour to process at the moment. 250 bars of
> 
> Ouch.
> Did you try setting gourlay_maxmeasures to a reasonable minimum?

I guess the problems aren't in the slow line-breaking: the
line-breaking process is linear in the length of the piece.  The
memory requirements are much more of a limitation: as soon as the
piece gets big, Lilypond will start swapping like crazy.  (And I think
that the space usage is is superlinear in the length of the piece, due
to the mechanics of the "breaking elements" step)

> did you strip the lilypond binary (and kill X etc?).

Stripping doesn't help, pages with symbol information aren't used when
running (so they're not even paged in when Lilypond is started)

-- 

Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter 
      http://www.cs.uu.nl/people/hanwen/lilypond/index.html 

Reply via email to