On Tue, 20 Apr 2010 11:41:25 -0300, Blower, Andy
<andy.blo...@proquest.co.uk> wrote:
Uber-component anti-pattern, not to my knowledge, but we have a lot of
pages and components now. And a lot of logic in them. The project's
large enough I can't be sure. Do you have a handy link to Howard's
description so I can get my team to check?
It's here:
http://old.nabble.com/-T5.0.18--Out-of-Memory-Error---Potential-Leak-(doesn't-reduce-after-forced-GC)-to25403474s302.html#a25497441
That thread is interesting, by the way. The problem is more about how
components and pages are written than the number of them.
What Tapestry version are you using?
Page pool config is default, I don't know enough to fiddle yet. Also,
the test is on a single stand alone server with no clustering, we are
using Tomcat clustering for production.
You should take a look a them, as they can affect the memory consumption
directly.
I did fire the GC manually before getting concerned BTW. A lot of heap
seems to be taken up with 100-300k descriptions on the
InternalClassTransformationImpl class. An example of one is attached
below - seems wrong to me and more like the debug that can be requested
through log4j rather than a description.
They look really bigger than they should. 300k is a lot. I have one
application with a reasonable number of pages and components and it runs
inside a 512 MB slide at SliceHost without using the whole memory.
--
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.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
