[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Han-Wen Nienhuys
Date: Wed, 13 Aug 2008 12:04:10 -0300
User-agent: Thunderbird (X11/20080723)

Ludovic Courtès escreveu:
> Hi Han-Wen,
> Han-Wen Nienhuys <address@hidden> writes:
>> I've implemented an env var GUILE_MAX_HEAP_SIZE (- some lilypond users
>> were complaining that running lily on large sets of files keeps
>> growing the heap forever, leading to trashing).
> Of course, the correct fix would be to help the GC be more reasonable,
> as it's currently somewhat broken:
> You could also try setting `GUILE_MAX_SEGMENT_SIZE' to a smaller value,
> as suggested there:

I'll have a think about this. Perhaps we can add a more stateful approach to 
the GC thresholds.

>> Please comment on the patch; it's in branch dev/hanwen on
> The patch contains mostly unrelated indentation changes, can you fix
> that?


> Also, it gives me the impression that we've definitely lost control over
> the GC code, and we're adding yet another configuration variable to work
> around that.  :-(

I'm not against initing it automatically to something like RAM * 0.8 or 
something, but that would run into portability issues.  In the end, the amount 
of RAM available is something that the current GC does not factor in, so it 
will happily grow the heap beyond that.  

 Han-Wen Nienhuys - address@hidden -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]