[Seaside] Home link

[Andrew Catton]

One thing I've noticed (in development images mostly) is that the
Monticello cache can grow quite large.  I've reset this cache and
garbage collected to bring 100MB images down to 15MB.

Cheers, Andrew

radoslav hodnicak wrote:

>On Fri, 5 Nov 2004, Avi Bryant wrote:
>
>  
>
>>So, after looking into this, I can't find a leak after all.  It may be
>>that the overhead of 2.5 is for some reason much higher than for 2.3
>>(which I'll have to fix), but in all of my experiments, you can keep
>>creating sessions or keep using a single session for as long as you
>>want and memory usage is fairly flat.  Has this also been your
>>experience, or does it just keep growing?  David, I know you also said
>>something about memory usage being higher for you now?
>>    
>>
>
>Well it can be that squeak simply isn't giving the memory back, if I stop
>wakom and release all handlers and do GC, the image still eats 160mb ram.
>
>  
>
>>As a more general question, how are people feeling about the recent
>>betas of 2.5?  I've been using it pretty heavily and it's been fine,
>>and don't know of any unresolved bugs, so it may be time to release
>>this thing.
>>    
>>
>
>Yeah I run it in production too and so far no problems
>
>rado (awaiting a message about a horrible crash right after finishing the
>above sentence)
>
>_______________________________________________
>Seaside mailing list
>Seaside at lists.squeakfoundation.org
>http://lists.squeakfoundation.org/listinfo/seaside
>  
>