Hi Andy, If you are running the defaults, then you might benefit from reducing the soft-limit of the pool, and increasing the hard limit, see this old thread: http://old.nabble.com/T5:-tapestry.page-pool.hard-limit-for-high-traffic-websites-td22971831.html
Cheers, Peter ----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Tuesday, 20 April, 2010 19:47:08 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Tapestry using 1.3Gb of heap space after capacity testing On Tue, 20 Apr 2010 13:41:37 -0300, Blower, Andy <andy.blo...@proquest.co.uk> wrote: > It looks like explicit repeated use of a component, rather than using a > single component in a loop, creates a lot more component objects in the > heap. Every <t:xxx> or <xxx t:type=""> is exactly one component, regardless of being inside a loop or not. When inside a loop, it's rendered many times, but instantiated just once, when the page instance is created. Static structure, dynamic behaviour. ;) -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
