I believe what you're seeing is just the way it is at this point in time. The extra time is used for things like building the Hivemind registry. If you turn on debug logging for Tapestry you'll see all the work that's being done at startup.
In this earlier posting: http://mail-archives.apache.org/mod_mbox/jakarta-tapestry-user/200509.mbox/[EMAIL PROTECTED] Howard said: I'm not thrilled with the slow startup of Tapestry 4, but it's a case of "get it right, then get it fast". I'll be looking at ways to speed up HiveMind for 1.2, then see if we can make use of that in Tapestry 4.1. I am pleased that runtime performance is good and, I suspect, better than 3.0. I agree that it's somewhat frustrating. After upgrading to Tap4, I've spent some time looking for the best development environment (trying things like JettyLauncher and JBossIDE) that would let me avoid restarting the server and Tapestry whenever possible. I haven't been a Spindle user before now, but I'm hoping the future Spindle4 will allow something like a hot-code-replace feature. Alexander Varakin wrote: >Hi, > >I noticed that in v4.0 first page display takes much longer than in v 3.0.3: >15 sec vs 7 sec. >I used the helloworld application for testing. >My environment is: > JBoss 4.0.2 (also tried Jetty and Tomcat, same result) > Sun JDK 1.5.06 > Intel Celeron 1.7GHz Laptop > 512 MB RAM > Debian Linux Unstable (also tried in Windows, same result) > >Is there any way to improve this time? > >Thanks, >Alex > > > >--------------------------------------------------------------------- >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]
