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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID Summary|-XSLTC -DIAG is incorrect |-XSLTC -DIAG is incorrect ------- Additional Comments From [EMAIL PROTECTED] 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.
