INFO: Techniques to Improve Performance of XSL Transformations
This article lists some techniques to improve the
performance of Extensible Stylesheet Language (XSL) Transformations. XSL is a
functional language. XSL does not support features of common language. For
example, XSL does not support return values, or globals. XSL is not an
object-oriented language, and being modular costs processor cycles. There is no
debug available for XSL, therefore, the debugging becomes
Performance of an XSL transformation depends on the
scenarios that you use. The techniques that are listed in this article are
general guidelines. Make sure that you measure the results of each tuning. Only
testing can prove whether a particular technique improves the performance or
not. You can use the msxsl.exe command line utility for testing, and to perform
command line XSL transformations by using the Microsoft XSL processor. The
msxsl.exe utility invokes the Microsoft XML Parser 4.0 (msxml4.dll) to perform
the transformation. You can download this utility from the following MSDN
Techniques to Improve the Performance
- Identify the most common code paths to render your pages,
and then optimize these paths. Optimize the highly re-used sections of
- Instead of using sub-elements, use attributes wherever
possible. Using attributes instead of elements improves the performance. When
performing XPath matches, attributes are faster because they are loosely typed.
This makes validation of the schema easier.
- Use more explicit paths instead of "//" wherever possible.
When XML data is large, "//" recursive decedent search is very expensive.
Specific XPath expression implements faster.
- When you match against attribute values, use enumerator
attributes. Use multiple attribute names as bits, and set their values to true or false. For example:
<element_name attr1="1" attr2="1" attr3="0">
- Do not use script. Using script downgrades the
- Compare directly by name to improve the performance. For
example, instead of using the following code: use the following code: When you compare values, instead of using name as follows:
use the following code:Because of the namespace handling in XPath, these are not exactly
- All versions of MSXML, Version 3.0 and later, are faster
with the explicit index filter. The improvement in performance depends on the
position of the element in the child list of the parent. Instead of using the
following: use the following:
- Use parameters instead of evaluating the query each
- XSL Transformations allows multiple options, however, all
of them may not perform adequately. For example, instead of using the following
use the following transformation:
This improves performance because indentation provides a lot of unwanted
white spaces in the output. By default, the value for the attribute indent is yes.
<xsl:output method="html" indent="no" />
- Inline the template with for-each or mode attribute when you are sure that your apply-template matches exactly one template. For example:
For each node that matches the following:
<xsl:apply-templates select="//xa:Axes/xa:Axis[@name='Axis1']" />
the following expression:
is evaluated on all other templates with the same mode. Processor starts
to run default templates. This copies all text nodes, and calls the following:for all elements. Therefore, for all children of original nodeset,
possible matches expression is evaluated. Matching the expression is not a
simple task. To improve the performance, rewrite the code as follows:
<xsl:apply-templates select="//xa:Axes/xa:Axis[@name='Axis1']/xa:Tuples/xa:Tuple" mode="Axis1"/>
<xsl:template match="*" mode="Axis1">
- Use fewer templates. This is applicable when you run the
same template more than one time. There is some improvement in performance with
tight for-each loop to search for a template when the number of templates are
- Reduce the usage of xsl:choose/xsl:when/xsl:otherwise. Performance is effected when the majority of selections fall
through the otherwise clause. Therefore, match with when, and try to avoid using otherwise when you know that a particular value exists.
- xsl:variables are dynamic values. These variables are not
in cache, and run every time that they are referenced in XSL. Explicit type
casting of xsl:variable improves the performance. You can do type casting with string() and boolean() functions. For example:MSXML Vs.
<xsl:variable name="_attr" select="string( /node/child[ @attr ] )">
- MSXML parser is different from XmlReader and XmlWriter.
- MSXML loads XML data into a Document Object Model
(DOM). From this DOM tree, data can easily be navigated through XPath,
transformed through XSL, or edited and saved back. This enables easier
development and more powerful capabilities at the expense of memory usage and
- XmlReader and XmlWriter are sequential readers and writers. The developer maintains state
manually when reading and writing XML data. This allows the minimal memory
usage and, therefore, improves the performance.
- The MSXML parser also supports SAX (Simple API for
XML). SAX is sequential. The .NET framework also supports the DOM by using the XmlDocument class.
- The best choice depends on the utilization of .NET
framework and on the task that you perform with XML.
- This technique is related to the performance with database.
MSXML and System.Xml performance can be improved in pre-joining the lookup
fields as shown in the following code:
You can avoid scanning by declaring @key of type ID.
<?xml version="1.0" encoding="UTF-8"?>
<Descriptor key="AMC_Labels_" ID="AMC" Name="-2000" TypeName="Labels" LCID="">
<Descriptor key="AMC_Labels_3082" ID="AMC" Name="-2000" TypeName="Labels" LCID="3082">
desc = doc.getNodeFromID("AMC_Labels_3082")
For more information, visit the following Microsoft
Developer Network (MSDN) Web sites:
For additional information about performance of XSLT,
click the following article numbers to view the articles in the Microsoft
INFO: Performance of XSLT
Transformations in the .NET Framework
Show Me How: Performance tune my Xslt Stylesheet in .NET using System.Xml
Article ID: 815124 - Last Review: November 2, 2007 - Revision: 2.4
- Microsoft .NET Framework Class Libraries 1.0
- Microsoft .NET Framework Class Libraries 1.1
- Microsoft .NET Framework 1.0
- Microsoft .NET Framework 1.1
|kbperformance kbxml kbinfo KB815124|