[Seaside] Possible for WADispatcherEditor references to be hanging around?

Yar Hwee Boon hboon at motionobj.com
Mon Nov 8 15:24:12 CET 2004


On Mon, 8 Nov 2004 15:13:20 +0100, Avi Bryant <avi at beta4.com> wrote:

> On Nov 8, 2004, at 3:07 PM, Yar Hwee Boon wrote:

>> Also, is it possible that if this is not done often, a large amount of  
>> memory will be taken up?
>
> That shouldn't be the case, though I suppose it depends what you  
> consider a "large amount".  Because of the way session expiry works  
> right now, it's possible to have sessions sticking around for quite a  
> long time on a seldomly used application, and so if your session does  
> something fairly memory intensive (like, say, caching a bunch of object  
> data from GOODS), you can easily end up with a 40MB image, as you saw.   
> OTOH, during active use, old sessions should be thrown out more  
> aggressively, and so the memory usage will stay flat (probably at a  
> similar level to what you have in your development image).  I haven't  
> heard any reports yet of images ballooning out of control (like, to 200  
> or 300MB) even during heavy use.

Thanks. That sets my mind at rest :)

-- 
Regards
HweeBoon
MotionObj


More information about the Seaside mailing list