On Sun, Dec 13, 2009 at 2:02 PM, Graham Percival <gra...@percival-music.ca> wrote: >> Oh wait - there is one thing I did not think about: snippets may be >> shared by different documents, > > Yes, that was my point about snippets being included in snippets.tely > and (for example) rhythms.itely. > >> For now, the easy fix is to use -j1 with CPU_COUNT for building the docs. > > Yes; that became the recommended way in Oct. But it's much slower > than it would otherwise be.
That surprises me. I thought the majority of the time was spent running LilyPond, which would be efficient with CPU_COUNT set, so the difference should be small. >> A more elaborate solution would be either some kind of locking, or to >> check whether the .ps / .pdf exists before actually processing the >> .ly; the latter is still suscepitible to races, though, but a check >> could make the opportunity window smaller. > > I think a .lock would be good. That's the typical solution to > everything when it comes to parallel processing. :) Right - the script should do an flock() on the database directory when opening it. (doesnt work on NFS though) -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
