[XSL-LIST Mailing List Archive Home]
Re: [xsl] Optimization Question
Subject: Re: [xsl] Optimization Question|
From: Michael Nguyen <mnguyen@xxxxxxxxxx>
Date: Tue, 01 Feb 2005 12:43:46 -0800
thanks for all the help. My lookup document (~5MB) is static. If I
were to do an xsl:include as opposed to me using a document call, would
using the compilier help? Is there someting I'm forgetting?
Robert Koberg wrote:
Michael Kay wrote:
Have you tried XSLTC. This basically allows you to apply a compiled
form of your stylesheet in your transformations. Both xalan and
saxon ship with XSLT compilers.
I'm asked occasionally whether I plan to do a Saxon compiler - more
strictly, a bytecode generator. At present, I don't: I think it would
down the rate of progress on the product considerably, if only
generators are notoriously hard to debug. I prefer to spend the
improving the query execution strategies, which can produce much bigger
potential savings. In any case, I think that for most people memory
of a constraint than processing speed.
I think this is a good idea. I usually run my app with Saxon and Xalan
interpretive(?). I occasioanlly run it also with XSLTC and Resin's
compiling processor (which requires much less memory and is the
fastest). I really wish I could use a compiling processor (especially
resin), but I always fallback to Saxon (its small and fast enough)
because it just works and there is always some little problem I run
into with compiling processors.
Senior Software Engineer, SKOLAR
Wolters Kluwer Health - Clinical Tools
1860 Embarcadero Rd, Suite 215
Palo Alto, CA 94303