Great replies!! Konstantin, creating a Filter is a good idea. I'll see if this can be implemented. This tool I'm using is not really a profiler, but a complete solution that hooks itself into the app server and monitors all method invocation -with its correspondent times- into a database. For the app I'm testing, I have more than 1,000 different method calls, although only two main HTTP requests. There is a request tree that shows the possible paths the requests have taken. And the times it is reporting are pretty close to the users' perception: 5.5 seconds / average.
Mark, you have a very good point about measuring each individual page; my problem is that the app is already in production, there is no test environment, and all measures were taken in one regular day -the profiler slowed things very much-. Nevertheless, all method calls have been logged, with call count, average cumulative time, avg exclusive time, etc. This is very data since calls to Spring's JdkDynamicAopProxy.invoke are taking as far as 2 seconds each! And this is exclusive time, which means it doesn't take into account the time inside the actual object that is being called... My main issue here is that it needs to be proven that Tapestry is not to blame for the slowness, and that having page information for the request analyzer would be great... Regards, Dario BTW, I cannot find information about JdkDynamicAopProxy being slow... I'm not such an expert on Spring, anyone knows if this might be a configuration issue? On 10/9/06, Mark Stang <[EMAIL PROTECTED]> wrote:
Well, then someone should change the text to say "shell rendering" time. Well, I hope his profiler shows the elapsed time for the method. Since there is are specific entry points he can profile those. Mark Mark J. Stang Senior Engineer/Architect office: +1 303.468.2900 mobile: +1 303.507.2833 Ping Identity -----Original Message----- From: Konstantin Ignatyev [mailto:[EMAIL PROTECTED] Sent: Mon 10/9/2006 4:21 PM To: Tapestry users Subject: RE: Thoughts about performance monitoring in Tapestry --- Mark Stang <[EMAIL PROTECTED]> wrote: > .... > The time spent in each page is at the bottom of each > page. Each page logs how long it took to render > itself. > > For one page: > <!-- Render time: ~ 1190 ms --> > > And for another: > <!-- Render time: ~ 209 ms --> > > > However, that is a total time, >.... Please look up old discussions regarding those numbers on gname, in short: the numbers have nothing to do whatsoever with real rendering time. See for example Howard's post http://article.gmane.org/gmane.comp.java.tapestry.user/15280/match=render+time Konstantin Ignatyev PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000 Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Some weasel took the cork out of my lunch. -- W.C. Fields --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
