No problems. I love the product, so anything to help it along (and get faster) I am happy to do. As a user, I would prefer that the lookups be cached. This may not include the TrAX, but I could live with it. The internal stuff.. I probably never would have even thought to muck with.
-- bk >> -----Original Message----- >> From: Shane Curcuru [mailto:[EMAIL PROTECTED] >> Sent: Thursday, May 30, 2002 10:15 AM >> To: [EMAIL PROTECTED] >> Subject: Re: Performance Improvements >> >> >> Hey - thanks for the suggestions! It's very useful to have such >> clearly laid out improvements, especially for the end-user and server >> manager side (as opposed to the inside the Xalan code side, >> which we're >> already working on). >> >> One note that I hope xalan committers can follow up on is #4 >> > 4) Set the following system properties: >> > >> > >> "org.apache.xml.dtm.DTMManager","org.apache.xml.dtm.ref.DTMMa >> nagerDefault" >> > >> "org.apache.xerces.xni.parser.XMLParserConfiguration","org.ap >> ache.xerces.par >> > sers.StandardParserConfiguration" >> >> While obviously we can't do anything directly about the >> xerces lookups, >> there was a suggestion somewhere to more quickly cache the values of >> the DTM manager lookups, and thus save additional .jar loads >> (I *think* >> the suggestion cached the found factory the first time it's found and >> saves it, thus bypassing all jar searches after the first one) >> >> >> ===== >> - Shane >> >> <eof aka="mailto:[EMAIL PROTECTED]" >> .sig="Du sublime au ridicule il n'y a qu'un pas." /> >> >> __________________________________________________ >> Do You Yahoo!? >> Yahoo! - Official partner of 2002 FIFA World Cup >> http://fifaworldcup.yahoo.com >>
