You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/10/23 21:00:12 UTC
DO NOT REPLY [Bug 13560] -
-XSLTC -DIAG is incorrect
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13560>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13560
-XSLTC -DIAG is incorrect
mkwan@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
Summary|-XSLTC -DIAG is incorrect |-XSLTC -DIAG is incorrect
------- Additional Comments From mkwan@ca.ibm.com 2002-10-23 19:00 -------
We record the currentTimeMillis before the call TransformerFactory.newTemplates
() and after the call Transformer.transform(). The time reported by the -diag
option is the difference between the two. I did not make any change to the way
the execution time is measured.
Regarding the execution time of Xalan vs. XSLTC, there is no guarantee that
XSLTC is always faster than Xalan. By default, the "-xsltc" option does not use
translet for transformation. It compiles the xsl on the fly and uses the in-
memory bytecode to do the transformation. From what I observed, XSLTC when not
using translet is mostly slower than Xalan, while XSLTC with translet is much
faster than Xalan.
If you use the -xt option to tell XSLTC use the translet, you will get an
execution time which should be faster than the time for Xalan.
Re: DO NOT REPLY [Bug 13560] - -XSLTC -DIAG is incorrect
Posted by Santiago Pericas-Geertsen <Sa...@sun.com>.
----- Original Message -----
From: <bu...@apache.org>
To: <xa...@xml.apache.org>
Sent: Wednesday, October 23, 2002 3:00 PM
Subject: DO NOT REPLY [Bug 13560] - -XSLTC -DIAG is incorrect
> ------- Additional Comments From mkwan@ca.ibm.com 2002-10-23
19:00 -------
> We record the currentTimeMillis before the call
TransformerFactory.newTemplates
> () and after the call Transformer.transform(). The time reported by
the -diag
> option is the difference between the two. I did not make any change to the
way
> the execution time is measured.
Perhaps it would make better sense to report both compilation time (before
TransformerFactory.newTemplates() until after Templates.newTransformer())
and execution time (before and after Transformer.transform()). XSLT
processing on the server side, where performance really matters, is
typically done by compiling once and running multiple times. Aggregating the
two numbers does not really help a user decide which processor is better for
a particular stylesheet.
In fact, I suggest the addition of #iterations to -DIAG to eliminate the
huge constant factor incurred on the first iteration as a result of things
like class loading (and also to see the effects of the JIT compiler). The -n
option of XSLTC's Process does exactly this.
My $0.02.
-- Santiago