On Fri, Mar 7, 2008 at 5:24 PM, Vesa Karvonen <[EMAIL PROTECTED]> wrote: [...] > Something as simple as keeping track of how much space is being used > and forcing a (full) GC each time it doubles after a previous GC could > do the trick. This policy would ensure that at most twice as much > memory is taken by C++ objects as necessary. The point of comparing > to usage at previous GC is to avoid doing GCs too often.
Note that the above bound for unnecessary space consumption needs to interpreted with respect to the required space consumption at the previous (full) GC (which is the known estimate). A single GC could cause almost all space taken by C++ objects to be freed, so the bound doesn't apply in the usual sense. I still believe the above kind of scheme would work quite well (not force GC too often and keep the space unnecessarily taken by C++ objects at acceptable levels). -Vesa Karvonen _______________________________________________ alice-users mailing list [email protected] http://www.ps.uni-sb.de/mailman/listinfo/alice-users
