Re: [xsl] XSLT performance under Linux

["Kurt Cagle" <cagle@xxxxxxxxx>]

I would recommend working with the xsltproc engine. It's C++ based, supports
a healthy subset of the Saxon parser, and is fast. I had something of a
jury-rigged system where I was calling saxon as a jar from the command line
(invoked from an `` expression in perl) and my system was crawling despite
being on a top of the line computer. I replaced it with xsltproc, and it was
a couple of orders of magnitude faster. It should be in most recent Linux
distros, though it's also up on Source Forge.

-- Kurt Cagle

----- Original Message -----
From: "Mattias Konradsson" <preacher@xxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, May 13, 2002 12:59 PM
Subject: [xsl] XSLT performance under Linux


> I'm working on a XSLT-based site which makes pretty extensive use of
> includes and whose output differens depending on params passed to it. The
> problem I'm having is performance. Since the site can be rendered through
a
> bunch of different skins and parameters are passed back and forth all the
> time output caching or pre-generating doesn't seem viable.
>
> My experience steems mostly from transforming under windows using MSXML or
> .Net. There you have the option of compiling stylesheets and caching the
> compiled stylesheet in the global cache for better performance but alas
the
> solution I'm working on now is running on Apache, currently with the
> Sablotron parser. So my questions are:
>
> 1. What's the best ways to increase performance without caching output?
Does
> any of the Apache parsers support above mentioned functionality?
>
> 2. Which parser should I chose for best performance, from reading some
> benchmarks it seems Saxon and XT seems to top the list?
>
> best regards
> ---
> Mattias  Konradsson
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list