Acutally, check the logging documentation; there's already a service that times how long the render takes and how many render operations were involved. Much of the performance improvements in 5.1 was reduce the number of operations per component.
There isn't a good way to get output about time per component; that time would be very short & hard to measure. Why are you interested in component render times? On Thu, Jan 15, 2009 at 4:35 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Thu, 15 Jan 2009 20:26:38 -0300, Fernando Padilla <f...@alum.mit.edu> > escreveu: > >> I was wondering if I could create some sort of profiler, that would print >> out the render time for each component.. >> that way I can use that information to try to pinpoint components that >> need to be optimized.. > > Quick and lazy :) answer: try to find the tapestry-core service that renders > components and decorate it using AspectDecorator . . . > > I hope it helps . . . > > By the way, AspectDecorator is absolutely awesome. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
