Manoj,
A couple of things to check (in no particular order):
1) Does the render time for a page change significantly between the
first *ever* render of that page within the JVM and subsequent renders? E.g.
if I hit the "refresh" button does the second render go materially faster?
2) Are you running any additional frameworks (like Hibernate) that
load on demand? If so they usually won't go through their (expensive)
initialization until the first page load of your app. Thus, in most of my
apps for example, first load takes 5.5 seconds (0.5 seconds for page, 5
seconds for Hibernate) and subsequent loads are fast.
3) Did you try instrumenting response time yourself? Override
HttpServlet and put your own timer and logging code around the doService
method. This will give you the *actual* amount of time the request handling
took, but will factor out Tomcat time and network time which will give you a
more accurate baseline to compare.
4) Do you have the Tapestry page pool off?
--- Pat
> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Manoj Prakash
> Sent: Saturday, September 03, 2005 4:28 AM
> To: [email protected]
> Subject: Performance problem : simple tapestry page takes long time to
> show up
>
> We have been using tapestry for over 1.5 years now for our app and
> recently we
> have started performance testing of this app. There are some interesting
> observations.
>
> Background/Environment:
> Server : P4 2.8 GHz,1 GB RAM, Windows xp, Tomcat 4.1.30, Tapestry 3.0 beta
> 4.
> Clients : P4 XP/Win2k machines with 512 MB RAM, accessing the server from
> different network.
>
> App: The first page of the app is a simplest login page, the html template
> is
> mostly static - has html form, refers a .css file, few images and input
> validation script( using tapestry's support for validation). We create a
> session ( by calling getVisit() ) on the login page itself before it is
> rendered.
>
>
> Problem:
> One a new browser instance, this login page takes consistently 18 to 20
> seconds to show up. Tomcat access log shows that it is taking upto 5
> seconds
> to process the login page request, another 5 seconds to process the
> request
> for validator.js, and almost negligible time to process the get requests
> for
> images and .css file. We are wondering why tomcat/tapestry is taking 5
> seconds
> to process the Get request for such a simple page.
>
> To rule out the network and tomcat, and other factors for this
> performance, we
> added a similar static html file, and a similar .jsp file in our webapp,
> and
> both show up within 3-4 seconds. Tomcat log in those cases show that it
> took
> only milliseconds to process the get request for .html and .jsp file.
>
> Any idea why this could be happening ? Is tapestry doing some heavy
> initialization work when a session is created? ( View source of the page
> in
> browser has 0 millisecond at the bottom as the render time).
>
> Thanks,
> Manoj
>
>
>
>
>
> ---------------------------------------------------------------------
> 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]
