On Sun, Mar 8, 2020 at 10:35 AM Han-Wen Nienhuys <[email protected]> wrote: > > To get back to your question: the consequences are worst when the job > > count is constrained due to memory pressure. My laptop has uncommonly > > large memory for its overall age and power, so I am not hit worst. The > > rough doubling of jobs does not cause me to run into swap space. > > I think something is off with the heap use (on GUILE 1.8 at least). We > can do the Carver score (which is 100 pages) in 900M heap easily. The > 600M number sounds too high, especially given the fact that the > snippets are generally tiny fragments of music.
GUILE 1.8: $ /usr/bin/time -v lilypond input/regression/mozart-hrn-3.ly .. Maximum resident set size (kbytes): 352280 GUILE 2.2 $ /usr/bin/time -v lilypond input/regression/mozart-hrn-3.ly .. Maximum resident set size (kbytes): 157904 I take some blame for this, because I wrote the heap stretching strategy for GUILE 1.8. -- Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen
