Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 84152 invoked from network); 15 Aug 2002 20:30:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Aug 2002 20:30:53 -0000 Received: (qmail 6454 invoked by uid 97); 15 Aug 2002 20:31:20 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 6438 invoked by uid 97); 15 Aug 2002 20:31:20 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 6419 invoked by uid 98); 15 Aug 2002 20:31:19 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: Thu, 15 Aug 2002 21:31:24 +0100 Subject: Re: Digester/Beanutils performance Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: robert burrell donkin To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N hi costin i've done some small scale timed tests (using the web ruleset from current tomcat). i've modified getMatchingAccessibleMethod so that it first tries to see if it can get the method directly before trying a method walk. this gives a large improvement (for my tests at least). i'll probably have a look at caching the methods later but it'd be very useful if you could run OptimizeIt against tomcat startup, measure the improvement and perhaps find some other high-pay areas to focus on. - robert On Wednesday, August 7, 2002, at 11:58 PM, costinm@covalent.net wrote: > I run few times OptimizeIt on tomcat startup. > > The parsing of server.xml takes about 4 secs on my machine, and >1/2 of > this ( 2.7 ) is in > MethodUtils.getMatchingAccessibleMethod() > > The same method seems to also double the time it takes for modeler > to load the .xml file - and I suspect other cases will be affected > as well. > > Solutions: > - cache the result and do something to optimize this. > > - use IntrospectionUtil from tomcat.util in Digester, which does > all the caching and has been optimized for quite some time. > > ( well, 4 secs to read server.xml doesn't seem too much - but things > add up quickly and someone may use this inside a servlet or something...) > > Costin > > > -- > To unsubscribe, e-mail: org> > For additional commands, e-mail: org> > -- To unsubscribe, e-mail: For additional commands, e-mail: