Now that is a really good advice. :-)
-Mensagem original-
De: kan [mailto:[EMAIL PROTECTED]
Enviada em: quarta-feira, 26 de novembro de 2008 14:19
Para: users@wicket.apache.org
Assunto: Re: Wicket Session grows too big real fast
I am not sure if it always applicable, but usually I do
Maybe would be a good idea if Wicket could report memory usage for
non-Wicket_Components (and non-standard Java objects, like String and
Collections) in memory. I don't know if this could ever be possible.
-Mensagem original-
De: Ladislav Thon [mailto:[EMAIL PROTECTED]
Enviada em:
Session/state-fullness is the no. #1 concern for me about Wicket. If you
like to keep an eye on certain object trees during runtime, as an
alternative to external profiling (which I've always found cumbersome)
you can use TopCoders memory usage component:
