Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <4116ABFA.9050009@apache.org>
Date: Sun, 08 Aug 2004 15:40:58 -0700
From: Brian Pane <brianp@apache.org>
User-Agent: Mozilla Thunderbird 0.7.3 (Macintosh/20040803)
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: StandardClassLoader ?
References: <cesj45$8rm$1@sea.gmane.org> <4111F1C1.7060508@apache.org>
 <cethn8$i5v$1@sea.gmane.org>
 <006401c47b00$e78b50a0$dd01dc0a@Corp.LaQuinta.com>
 <411259F7.7050402@apache.org> <cf059g$s78$1@sea.gmane.org>
 <41139BB5.7080104@apache.org> <cf07ev$2fo$1@sea.gmane.org>
 <4113BB21.4030800@apache.org>
In-Reply-To: <4113BB21.4030800@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Remy Maucherat wrote:

> I agree. I'm kinda running out of optimization ideas, though (I don't 
> know if you profiled the regular request processing lately, but 
> there's really nothing left). There doesn't seem to be too much which 
> is doable with the startup overall.


I've found that the parsing of the default server.xml during Tomcat
5.0.27 startup takes 1.5 seconds on my test system.  In comparison,
the SAX-based element-counter sample program shipped with Xerces-J
takes less than 100 ms to parse the same file on the same hardware.
Based on this, my hypothesis is that the SAX callback handlers in
org.apache.tomcat.util.digester.Digester may account for a lot of
the parsing time.  Does that match what you've found in your profiling?
(I only have coarse-grained profiling data from adding
System#currentTimeMillis calls to the Tomcat code.  I haven't yet
figured out how to use "-Xrunhprof" without slowing Tomcat to a crawl.)

Brian


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org