Re: XSLT performance under Linux

Am Montag, 13. Mai 2002 22:15 schrieben Sie:
> I would recommend working with the xsltproc engine. It's C++ based,
> supports a healthy subset of the Saxon parser, and is fast. 

It´s much faster than saxon, but pay attention if you are using some 
xslt 2.0 (1.1) features like "result tree fragment to node-set" 
conversion. and there are still some other things even from the 1.0 
specs which doesnt seem to work with xsltproc (overriding attributes 
in a tag). I switched from saxon to xsltproc but can be a big effort 
to do. Just dont expect to exchange your parser command and expect it 
to work. I also found an annoying difference in handling whitespace, 
but most things i havent heavily tested, some of them i tested and 
found a bug (already reported, of course).

But after all: xsltproc is the fastest engine, but i guess saxon is 
the one which is most compliant with the specs. 

For me xsltproc is four times faster. the german magazin 'iX' 
benchmarked most important engines April 2002 (heise.de/ix/)

regards, 
janning  

>
> -- Kurt Cagle
>
> ----- Original Message -----
> From: "Mattias Konradsson" <preacher@xxxxxxxxxxx>
> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Monday, May 13, 2002 12:59 PM
> Subject:  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

-- 
Planwerk 6 /websolutions
Herzogstraße 86
40215 Düsseldorf

fon 0211-6015919
fax 0211-6015917
http://www.planwerk6.de

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