[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUILE GC -- Write barrier for vectors
From: |
Han-Wen Nienhuys |
Subject: |
Re: GUILE GC -- Write barrier for vectors |
Date: |
Mon, 15 Jul 2002 13:00:19 +0200 |
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/
- GUILE GC -- Write barrier for vectors, hanwen, 2002/07/14
- Re: GUILE GC -- Write barrier for vectors, Miroslav Silovic, 2002/07/15
- Re: GUILE GC -- Write barrier for vectors,
Han-Wen Nienhuys <=
- Re: GUILE GC -- Write barrier for vectors, Dirk Herrmann, 2002/07/15
- Re: GUILE GC -- Write barrier for vectors, Han-Wen Nienhuys, 2002/07/15
- Re: GUILE GC -- Write barrier for vectors, Dirk Herrmann, 2002/07/15
- Re: GUILE GC -- Write barrier for vectors, Han-Wen, 2002/07/15
- Re: GUILE GC -- Write barrier for vectors, Han-Wen Nienhuys, 2002/07/16
- Re: GUILE GC -- Write barrier for vectors, Dirk Herrmann, 2002/07/16
- Re: GUILE GC -- Write barrier for vectors, Han-Wen, 2002/07/16
- Re: GUILE GC -- Write barrier for vectors, Han-Wen, 2002/07/17
- Re: GUILE GC -- Write barrier for vectors, Dirk Herrmann, 2002/07/19