Re: GUILE GC -- Write barrier for vectors

[Han-Wen Nienhuys]

address@hidden writes:
> >Can anyone comment on how to improve the performance?
> >  
> >
> I had a similar problem when working with a large number of  vector-like 
> things - basilly
> my application would trigger GC more often than necessary. The reason 
> was that I didn't
> properly report bytes allocated to Guile (i.e. my use of scm_must_malloc 
> was broken).

> If you're reporting too much, the GC will trigger all the time. 
> Alternatively, if you're reporting

I'm quite sure that free/malloc bytes reported are matched. However,
most counts are a little underestimated. This is impossible to
prevent, since we are using classes derived from smobbed C++
baseclasses (You can't get correct object sizes in destructors and
constructors).

-- 

Han-Wen Nienhuys   |   address@hidden    | http://www.cs.uu.nl/~hanwen/