Re: [Squeak-VMdev] Re: GC improvements

[Andreas R. <and...@gm...>]

Hi John,

> Ok, I consolidated all of this, added a prim to turn the biasGrowth 
> behavior on where the grow and post fullGC logic is in the interp.c  code, 
> versus being partially in the image. Also a prim to set the  threshold for 
> doing the fullGC if we have grown by N bytes. Thus you  can turn off/on 
> and set the boundary. Left in the other prims as  agreed.

Thanks, this sounds good.

> a) The 10 entries I have for FinalizationDependents have sizes of #(0 2  0 
> 3 2 55825 nil nil nil nil). You will note the one with 55,825  entries. 
> This actually a 98K or so WeakIdenityKeyDictionary of  CompiledMethods.

This is not the case in any image I am using. You must be using a 
non-standard image; all the regular ones that I've checked have  #(0 2 nil 
nil nil nil nil nil nil nil) (0: Sockets; 2: Files).

> which leds to signaling the FinalizationSemaphore which wakes up the 
> FinalizationProcess which calls finalizeValues on each WeakArray
> instance (and subclass instance) That has some issues.

Correct. But this has always been the case and is not a result of the recent 
changes.

> PS Isn't it a bit ugly to iterate over all the elements of Weak things 
> looking for null entries, versus passing up a cluestick?

Yes it is. But remember: Passing a cluestick requires an (unbounded) amount 
of memory which is why I never considered it.

Cheers,
  - Andreas