I think you just need to use the @Shell component. On 9/26/06, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
I believe if your set the log level for tapestry to "debug", as in putting a line like "log4j.logger.org.apache.tapestry=debug" in your log4j.properties, it will output such information. Like 19:30:56,135 DEBUG BaseComponent:89 - Begin render Home 19:30:57,807 DEBUG BaseComponent:95 - End render Home It would probably be nicer to see the actual time amount then just the two logging timestamps... I guess you could just modify/overwrite BaseComponent.renderComponent to output that. Hth, Lutz On 9/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi. I'm wondering if anyone has done any simple timing of the processing for a page? > > I've changed my border slightly so at the start it creates a Date, and at the end creates another and determines the difference. > > However, I think this only works out to be the render time of the page itself, not the processing time to get all the information for that page (eg. slow DB queries). > > Maybe something like this would go in a Servlet method? I'm really unsure. > > Anyone have any insight? This way I can work on tuning my application and have some hard numbers to see if, on average, they are getting smaller or not. > > Thanks, > Greg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
