----- Original Message -----
From: "Reinhold Kainhofer" <reinh...@kainhofer.com>
To: "Julien Rioux" <jri...@physics.utoronto.ca>
Cc: <lilypond-devel@gnu.org>; <bug-lilyp...@gnu.org>
Sent: Thursday, January 26, 2012 4:13 PM
Subject: Re: make doc problem
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem here is that lilypond builds up memory from 400MB to ~1GB
without releasing...
Most of these allocations don't seem to be memory leaks, but rather due
to guile.
Cheers,
Reinhold
It only takes that amount of memory for big builds. I've never seen much
over 1 Gig total memory during a make with 8 CPUs all running lilypond.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
