Yuan,

There is not much of a performance difference between XSLTC and
interpretive XSLT processors unless the stylesheet is somewhat
complex. Most people do the mistake of using an identity
transformation (a pure copy) when comparing the performance of
XSLT processors. What you are doing then is in effect testing the
performance of your XML parser, as 75-85% of the processing time
is spent parsing the input document. If you want to run some
proper performance comparisons you will need a stylesheet with
a bit of "meat".

Thanks,
Morten Jorgensen


> -------- Original Message --------
> Subject: a performance comparison in Xalan2
> Date: Wed, 15 Aug 2001 19:41:03 -0400
> From: "Cheng, Yuan" <[EMAIL PROTECTED]>
> To: "'Tom Amiro'" <[EMAIL PROTECTED]>
> 
> Hi Tom,
> 
> I compared performance of transformer implementation of xalan and xsltc in
> Xalan2J TrAX/JAXP interface (Xalan-j_2_2_D9), i.e.,
> org.apache.xalan.xsltc.trax.TransformerImpl and
> org.apache.xalan.processor.TransformerImpl.
> 
> I captured exe time on transformer.transform() function (I used bw.xml and
> opAndSelf.xsl for testing).
>                     Xalan             Xsltc
> avg time             718 ms           756 ms
> 
> What supprised me is that xalan seems to out-perform xsltc when xml parsing
> and transformation are evaluated together. ( I looked into their
> implementations of transformer.transform(), whose operations include parser
> creation, xml parsing, xsl transformation, etc., but not include translet
> creation.)
> 
> Is this true? I would appreciate your comments.
> 
> thanks,
> Yuan
> ps: transformerTest.java
> 
>   --------------------------------------------------------------------------------
>                            Name: transformerTest.java
>    transformerTest.java    Type: unspecified type (application/octet-stream)
>                        Encoding: base64

Reply via email to