Hi Mike,
I don't know what XSLT profiler you are referring to. The Saxon profiling
I was using the Stylus Studio profiler -
http://www.stylusstudio.com/xslt_profiler.html
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.
Nothing elaborate, I just set -Xrunhprof:cpu=samples on the command line and
looked at the resulting java.prof.txt 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.
Many thanks, again.
- Sujata
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--