On Monday 01 Jul 2002 2:32 pm, Michael Kay wrote:
> > We have been trying to determine whether using XSL:For-Each
> > is having an impact on the speed of our document publishing.
> > Some of my buddies don't want to use xsl:for-each because
> > they believe it causes the process to take a longer amount of
> > time than just doing a template match over and over. Is this
> > true or no? Is xsl:for-each a performance hog or does it and
> > template matching take the same amount of time?
>
> Measure it and see. The results will depend on which XSLT processor you
> are using. My guess is that there will be very little difference. The
> arguments against xsl:for-each are based on maintainability, not on
> performance.
>

And the complexity of the template match expressions in the stylesheets. 
Simple tests on name or nodetype can be efficient but matches that involve 
predicates are generally harder for a processor to index. These can cause 
some processors to use sequential searching for a templates (slow for large 
numbers of templates). I have seen the performance of some stylesheets 
completely cripled by use of complex matches, e.g.,

<xsl:template match="m:apply[child::*[position()=1 and name()='factorof']]">

So its very specific to a processor/stylesheet pair and complex tests are 
better done in for-each/if blocks if performance is more important than 
maintainability.

Kev.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list