What are your values for the tapestry.page-pool.* symbols? Have you tested
making 1k or 10k request and then taking another used memory reading?
Some time ago, someone here (sorry, I forgot the name) posted a test like
the one I'm suggesting above (a load test). It found out that Tapestry,
after a large load, had its performance back to normal (i.e. before the
large load).
On Tue, 09 Feb 2010 08:48:57 -0200, Jim O'Callaghan
<j...@peritussolutions.com> wrote:
Looking at the memory (private working set) used by the java process my
Tapestry 5 app is running under, I notice that when running through the
same
request cycle with PRODUCTION_MODE set to true, I am getting an increase
of
approx 4K per repeated request. Is this typical or something to be
concerned about in the context of an application with >50 <100 concurrent
users, or is Tapestry reasonably aggressive in reclaiming resources? If
it
is not typical, any pointers on areas to look for leaks, or is this a
needle
in a haystack?
Thanks,
Jim.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
Coordenador e professor da Especialização em Engenharia de Software com
Ênfase em Java da Faculdade Pitágoras
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
Sócio, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
