Howdy, I would add Coyote as another big change from the older HttpConnector.
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Bill Barker [mailto:[EMAIL PROTECTED] >Sent: Thursday, April 03, 2003 4:30 AM >To: [EMAIL PROTECTED] >Subject: Re: Tomcat 4.1 slower than Tomcat 3.3 > >Well, the big performance change in TC4.1 over TC3.3 is Jasper2 vs. >Jasper1. >For heavy JSP sites, my benchmarks say that TC4.1 wins. > >Since it seems that you aren't using JSP at all, it isn't surprising (to me >at least :) that the extra over-head of supporting the 2.3 Servlet spec >drags down TC4.1 vs. TC3.3. For non-JSP sites that don't require >Servlet-2.3 features, it is very hard to beat TC3.3 for performance. > >"Chris Agmen-Smith" <[EMAIL PROTECTED]> wrote in message >news:[EMAIL PROTECTED] >> Is Tomcat 4 slower than Tomcat 3? >> >> I've recently tried to port my Tomcat 3.3 webapp to Tomcat 4.1. It's the >> same webapp, the config files are as similar as I can make them, we're >using >> the same connector to Apache. However, Tomcat 4.1 chews up CPU like you >> wouldn't believe. >> >> Example: at peak load, one of our Tomcat 3.3 servers served 20,000 page >> impressions in an hour, at an average %usr CPU of 60%. Using Tomcat 4.1, >we >> can only serve about 7,000 pages if we down-weight it so that it is at >60%. >> >> Old setup: >> Apache 1.3.x -> AJP 1.3 -> Tomcat 3.3.x -> webapp (uses Velocity 1.2 & >> Turbine 2.1) >> >> New setup: >> Apache 1.3.x -> AJP 1.3 -> Tomcat 4.1.x -> webapp (uses Velocity 1.2 & >> Turbine 2.1) >> >> We have tried profiling the app using hprof and these are the results: >> Method Tomcat 3 Tomcat 4 >> java.net.URLEncoder.encode 33.62% 22.60% >> java.net.SocketInputStream.read 14.15% 18.77% >> java.net.SocketOutputStream.write 1.87% 3.47% >> >> The encode method is used by Velocity and Turbine to generate URL links. >For >> this particular test, T4.1 used about 1.5 times the CPU that T3.3 used. >> Given that the same number of pages & therefore links are being >generated, >I >> think this shows that T4.1 is spending significantly more time in >> SocketInputStream.read that T3.3. >> >> I have tried to following tuning options, even though they weren't needed >in >> T3.3: >> - Removed servlet filters (no effect; not used in T3.3) >> - Reduced logging to bare minimum (no effect) >> - Experimented with numerous JVM >settings: -server -d64 -Xmn256mb -Xmx384mb >> -Xconcurrentio (no effect) >> - Tried latest Solaris patches (no effect) >> - Tried 64-bit java (no effect) >> - Changed maxProcessor (# of threads) from default to 20 to 50 to 100 etc >> (no effect) >> - Changed Java/Solaris threading libraries (no effect) >> >> I don't have any more ideas how to fix it; instead I am clutching at >straws >> :o) Some of those straws include: >> - Tuning/hacking/fixing Turbine, in case it is incompatible with the >Servlet >> 2.3 spec. >> - Trying even more JVM setting permutations, in the hope that I come >across >> the "magic" combination. >> - Disabling socket keepalive in Apache. >> >> Until we can fix this, we are sticking with Tomcat 3.3, which has so far >> been stable, fast and robust (except for allowing sessions between https >and >> http). >> >> Chris Agmen-Smith >> >> >> ________________________________________________________________________ >> This email has been scanned for all viruses by the MessageLabs service. >> ________________________________________________________________________ > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
