This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: memory usage


Christian Lynbech <chl@tbit.dk> writes:

> >>>>> "Lynn" == Lynn Winebarger <owinebar@free-expression.org> writes:
> 
> Lynn> ... grow to 183 megs! 
> 
> It sounds very much like you have been bitten by the heap growth
> algorithm.
> 
> The default algorithm is (when the need to expand the heap has been
> identified) to allocate a new segment twice as big as the previous
> segment, which isn't so hot when you have a medium sized requirement
> on heap size.

The issue is that it shouldn't -need- to grow. Heap growth only
happens if GC hasn't freed enough memory, and that should only happen
if the memory gets allocated too much.

In my experience this happens if SMOB free routine doesn't cleanup
correctly, or if it returns the wrong value for the ammount of memory
that got freed (the latter thing can really bite you).

-- 
How to eff the ineffable?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]