On Thu, 02 Sep 2010 18:30:49 -0300, Howard Lewis Ship <[email protected]>
wrote:
One of my long term and unrealized goals for Tapestry is to have a
legitimate performance testing lab.
Cool!
I'd like the ability to run a "standard" application through its
paces, collect statistics, and see how well each new Tapestry release
compares to its predecessor in terms of general performance: response
time, memory utilization, saturation and recovery. Ideally, it would
be nice to create equivalent JSP/Spring MVC/Struts/Wicket
implementations of the same app.
I've done something a little similar, but in a smaller scope, for a
presentation comparing Struts 1, Struts 2, JSF and Tapestry 5. I
implemented a simple application, DAOs and simple business rules layer,
and them implemented its web interface using each of the frameworks.
I'm really concerned with ensuring that 5.2 out-performs 5.1, and uses
less memory. The singleton pages approach should lower the memory
utilization ... but I'm concerned that the new AOP stuff inside
ClassTransformation (which has a tendency to create lots of little
one-off classes) will overshadow the other improvements.
Someone in the mailing list mentioned Parfait
(http://code.google.com/p/parfait/wiki/IntroductionToParfait). It could be
helpful for that.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
