Hello. In the Tomcat 6.0 Jasper documentation at <http://tomcat.apache.org/tomcat-6.0-doc/jasper-howto.html#Production%20Configuration> or <http://LNK.by/c2H2>, I read that the most performance gain can be achieved by pre-compiling the JSPs. Because of that, I simply gave that a try and can't find much of a gain at all.
I used Ant 1.8.0 with Java 1.6.0_18 and the build.xml script at http://pastebin.ca/1828486 We're doing around the clock "performance measurements", where some Watir based script runs a browser and calls pre-defined pages and tasks in the web app. We measure, how long this takes. Please see http://goo.gl/cokf for a graph showing this. "Yesterday", at about 16:00, I installed the pre-compiled web app. There's no (visible) change in the measurements to be found. Did I do something wrong? Was the build.xml not good (enough)? I invoked it with: tomcat_home=/usr/share/tomcat webapp_path=/var/webapp ant "-Dtomcat.home=$tomcat_home" "-Dwebapp.path=$webapp_path" Or is it just, that this shows, that our web app doesn't have a bottleneck in the "JSP land" (which would be a true statement - it communicates with some background databases and apps, which might not be the fastest...)? One thing which confuses me a bit though, is that when I call the web app for the first time (after deployment or after having re-started Tomcat), the web app is "slow". Ie. I go to http://server:8080/webapp and wait for like 10 seconds until the login screen of the web app is shown. This wait only happens for the very first time after deployment. When I do this again a few minutes/hours later, http://server:8080/webapp is shown right away. Shouldn't pre-compilation also make this first time wait go away? Thanks a lot, Alexander --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
