[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] Perfomance: 'conditional instruction' vs. 'multi template'


Subject: Re: [xsl] Perfomance: 'conditional instruction' vs. 'multi template'
From: Michael Kay <mike@xxxxxxxxxxxx>
Date: Sat, 03 Nov 2012 16:55:50 +0000

I usually prefer approach 1 because the code is more concise and more readable / reusable / extensible / customizable.

Performance will depend on the processor. Most processors are likely to do a linear search of the alternatives in both cases, so it's unlikely to make much difference (if you're interested in performance, then measure it!). Some processors may have optimizations for special cases, but I don't think that should influence your choice unless you need to squeeze the last ounce of performance: and if you need to do that, the most effective solution is usually to upgrade your hardware. It's certainly not a case where what's fastest on one processor will be fastest on every processor.

Michael Kay
Saxonica

On 03/11/2012 15:24, Norbert Heidbrink wrote:
Hi everybody,

if a node is to be processed differently, depending on a certain
condition, there are two approaches.

Let's say, the condition is "existance of child x".


Approach 1: two templates with different matching XPaths


<template match="thenode[child::x]">
   b& do_this b&
</template>

<template match="thenode[not(child::x)]">
    b& do_that b&
</template>


Approach 2: one template with a conditional instruction


<template match="thenode">
   <xsl:choose>
   <xsl:when test="x">
     b& do_this b&
   </xsl:when>
   <xsl:otherwise>
     b& do_that b&
   </xsl:otherwise>
</xsl:choose>
</template>


I wonder, if one of these approaches is to be favoured? Are there any severe implications on performance? Any other advantages / disadvantages that speak in favour of approach 1 or approach 2?

I am curious to read your estimations,
Norbert


Current Thread