1) The render time in the bottom of the page is totally misleading. It tells you how long it took for Tapestry to execute the code that produces the HTML inside the shell component. That is all. If you have an activate or anything precomputed before the shell is invoked (rewind cycle for instance), that is not reflected. The web server access logs will give you a better idea of performance.
2) I don't understand why you think this is a Tapestry problem. Sounds like something is wrong in your Tomcat installation. You say that a .jsp page takes between 3 to 4 seconds while the Tapestry page takes 5 seconds. So clearly your Tomcat installation has issues. ----- Original Message ----- From: "Manoj Prakash" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, September 03, 2005 7:28 AM 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]
