In my two previous posts I described a potential performance hit caused by XSLT-to-MSIL compilation and JIT-compilation when you load and run some XSLT stylesheet with the XslCompiledTransform engine for the first time. Since the .NET Framework 2.0 did
Read More...
Interestingly enough, the first live.com hit for
the "XslCompiledTransform Performance" query at the moment is
this post
of Jeff Prosise, where he says he was disappointed that XslCompiledTransform
ran just 3 times faster than XslTransform on a "fairly simple style sheet".
He is concerned that XslCompiledTransform is not fast enough comparing to
the good old MSXML 4.0. Well, as we will see very soon, XslCompiledTransform
may easily outperform MSXML 4.0 by several times!
Read More...
The .NET Framework 2.0 provides a new
System.Xml.Xsl.XslCompiledTransform XSLT processor class, which is intended to replace the obsoleted
XslTransform class. One of the major differences between the two is that while the latter is an XSLT
interpreter, the former is a real XSLT
compiler, allowing significantly faster execution times. Does it mean
XslCompiledTransform is always faster? Surprisingly, the answer is not that simple.
Read More...
Attachment(s): XsltPerf.zip
