Signs on the Sand

Thank you. I'm no happier but I feel much saner. I will report it on MSDN.
Kaylee

Yeah, I get 875 ms compilation time. Is it too much for your application? If so, file a bug at MSDN feedback center, I believe compilation can be done a bit faster.

I'm lost...

The C# code (I know it's convoluted but I will eventually be getting BOTH the xml and xsl as strings):

public static void Main()
{

int start, stop;

//get the xsl as a string
StreamReader xslr = new StreamReader(stylesheet);
string xslStr = xslr.ReadToEnd();
Console.WriteLine(xslStr);

//get the xml as a string
StreamReader sr = new StreamReader(filename);
string inStr = sr.ReadToEnd();

start = Environment.TickCount;
// Load the style sheet.
StringReader xslReader = new StringReader(xslStr);
XmlReader xslRdr = XmlReader.Create(xslReader);
stop = Environment.TickCount;
Console.WriteLine("\nXSLLoad time in ms: {0}",(stop - start).ToString());

start = Environment.TickCount;
XslCompiledTransform xslt = new XslCompiledTransform();
stop = Environment.TickCount;
Console.WriteLine("\nCTCreate time in ms: {0}",(stop - start).ToString());

start = Environment.TickCount;
xslt.Load(xslRdr);
stop = Environment.TickCount;
Console.WriteLine("\nCTLoad time in ms: {0}",(stop - start).ToString());

start = Environment.TickCount;

//Load the xml
StringReader strReader = new StringReader(inStr);
StringWriter strWriter = new StringWriter();
XmlReader reader = XmlReader.Create(strReader);
stop = Environment.TickCount;
Console.WriteLine("\nXmlLoad time in ms: {0}",(stop - start).ToString());

start = Environment.TickCount;
// Transform
xslt.Transform(reader, null, strWriter);
stop = Environment.TickCount;
Console.WriteLine("\nTransform time in ms: {0}",(stop - start).ToString());

}

and here's the little stylesheet that's causing the problems (again, convoluted, because of all the testing):
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<RESULTS>
<xsl:apply-templates select="node()"/>
</RESULTS>
</xsl:template>
<xsl:template match="ITEM">
<xsl:if test="boolean(./CUSIP='037023108')">
<xsl:copy-of select='.' />
</xsl:if>
</xsl:template>

<xsl:template match="node()">
<xsl:apply-templates select="node()"/>
</xsl:template>

</xsl:stylesheet>

Thanks,
Kaylee

Make sure you are not running in debug mode (bool argument to the XslCompiledTransform constructor).
Can you send the code me so I could try to reproduce the problem?

It's a very simple stylesheet that I developed specifically for testing. It has a couple of templates. One handles the generic case (node()) but does nothing except apply-templates. The other is looking for a specific case and will do a copy-of that node if found.
The relevant portions of the code were taking less than a half second on 1.1. The XslCompiledTransform.load() (with xmlReader as an arg) alone is taking 1283 ms on 2.0. I've checked it several times because I was incredulous.

Well, it compiles XSLT down to MSIL and assembly, but it should't be deadly slow. What kindof stylesheet and how you run?

I have been doing some performance testing. I am comparing XSL transform performance between Framework 1.1 and 2.0. I must be doing something wrong. I am getting some huge numbers when doing a XslCompiledTransform.load(). I realize that it is doing extra work but the load is killing me. Any suggestions?

This sucks. I've only just mastered (to some kind of beginner level) XslTransform, thanks mainly to Oleg and Daniel Cazzulino's writings (blogs and MVP.XML).

The annoying part is the MSDN page on how to migrate from XslTransform to XslCompiledTransform convieniently ignores the overloads of transform that return the XmlReader.

http://winfx.msdn.microsoft.com/library/default.asp?url=/library/en-us/wd_xml/html/9404d758-679f-4ffb-995d-3d07d817659e.asp

With Beta 2 out, what are the chances of this being changed back before the final version?