Hi Frank

We had the same problem for a Seaside application with quite some load. 
The problem ist that with the amount of data that Seaside caches the 
finalization process just takes too much time to walk over all the 
objects.

There is a simple solution, with tradeoff between space and cpu: In 
SeasidePlatformSupport class>>weakDictionaryOfSize: remove the 
registration of the Dictionary by commenting out the line "WeakArray 
addWeakDependent: dict."

The image we use grows up to about 200MB max which is totally ok.

Hope this helps,
Adrian



On Mar 3, 2005, at 3:58 PM, Frank wrote:

> I noticed that my squeak development image is getting very slow. For 
> example when switching windows I wait about one second. Opening a 
> browser takes several seconds.
>
> The only odd thing I found is that when I switch windows the weak 
> array finalization process in the process window peaks at 82% cpu 
> usage.
>
> My squeak image 3.7 runs on OSX (800 MHz powerbook) and is used to 
> develop a Seaside application.
>
> What I would like to know is:
>
> 1. What causes the slow down
>
> 2. How can I correct the problem
>
> Any ideas?
>
> Best Regards,
>
> Frank
>
>
>
___________________
Adrian Lienhard
www.adrian-lienhard.ch
www.netstyle.ch