Altova Mailing List Archives

RE: [xsl] Optimizing XSLT iteration

From: "Michael Kay" <mike@------------>
Date: 10/8/2007 5:59:00 AM
> When I run XSLT profiler, 

I don't know what XSLT profiler you are referring to. The Saxon profiling
tool only tells you how much time is spent in each template, which is not
very useful here as everything is in one template. Generally, finer
resolution than this is not necessarily helpful because XSLT processors do a
lot of lazy evaluation, which means costs are not always incurred at the
point where the costly expression is written.

> Please do let me know the tools you are using.

Nothing elaborate, I just set -Xrunhprof:cpu=samples on the command line and
looked at the resulting file, which immediately revealed (to
someone who knows the Saxon internals, at any rate) that at least 90% of the
time is spent evaluating xsl:number.

Michael Kay


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.