[Seaside] WARegistry performance
ssastre at seaswork.com
Fri Dec 26 17:28:54 UTC 2008
I was able to see in the dump that, at freeze time, the image was trying to send me a walkback by email about an out of memory error.
As it was unresponsive I've terminated the process. It wasn't formally an image crash but it was maintenance related.
Maybe I have to include some periodical task like making once per day some housekeeping action.
Any pointers, best practices to that housekeeping? One WARegistry clearAllHandlers is all we can do for this? Do that destroy currently alive sessions?
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Philippe Marschall
> Enviado el: Viernes, 26 de Diciembre de 2008 15:01
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] WARegistry performance
> 2008/12/26 Sebastian Sastre <ssastre at seaswork.com>:
> >> Can you provide a bit more information? Are the delays
> only the first
> >> few requests or ongoing? What does WASession
> allSubInstances say? Does
> >> WARegistry clearAllHandlers help? How many open processes
> do you have?
> > Sadly, when I waws about to check this, the image already crashed.
> Do you have the SqueakDebug.log?
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside