|
From: | Aaron Hill |
Subject: | Re: LilyPond can't engrave 16 pages of music |
Date: | Fri, 21 Dec 2018 17:07:51 -0800 |
User-agent: | Roundcube Webmail/1.3.6 |
On 2018-12-21 4:53 pm, Aaron Hill wrote:
I tried the following approach to break up the piece into three scores: %%%% \score { { \time 4/4 \repeat unfold 1000 { c4 d e f } } } \score { { \set Score.currentBarNumber = #1001 \bar "" \time 4/4 \repeat unfold 1000 { f1 } } \layout { indent = 0 } } \score { { \set Score.currentBarNumber = #2001 \bar "" \time 4/4 \repeat unfold 1000 { c4 d e f } } \layout { indent = 0 } } %%%%This only took 42 seconds to complete and I believe it peaked under 2GiB.
I reran my multi-score version using time -v: Command being timed: "lilypond allocbug.ly" User time (seconds): 32.29 System time (seconds): 9.48 Percent of CPU this job got: 99% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:42.05 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 1978288 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 1003509 Voluntary context switches: 0 Involuntary context switches: 0 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0Providing this is accurate, I suspect this approach may still be too much for a 32-bit process, given the overhead of the program executable, DLLs and the like.
-- Aaron Hill
[Prev in Thread] | Current Thread | [Next in Thread] |