<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: XSLT Profilers</title>
	<atom:link href="http://www.onenaught.com/posts/56/xslt-profilers/feed" rel="self" type="application/rss+xml" />
	<link>http://www.onenaught.com/posts/56/xslt-profilers</link>
	<description>A blog on web standards, accessibility, css, javascript, xslt, and more</description>
	<lastBuildDate>Fri, 30 Jul 2010 12:54:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Anup Shah</title>
		<link>http://www.onenaught.com/posts/56/xslt-profilers/comment-page-1#comment-13981</link>
		<dc:creator>Anup Shah</dc:creator>
		<pubDate>Fri, 14 Aug 2009 21:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/56/xslt-profilers#comment-13981</guid>
		<description>@Aaron: unfortunately I don&#039;t know the answer to that. I have not used the profiler for a long time now, but from what I recall it was just based on simple XML file input... Do let me know if you find a way...</description>
		<content:encoded><![CDATA[<p>@Aaron: unfortunately I don&#8217;t know the answer to that. I have not used the profiler for a long time now, but from what I recall it was just based on simple XML file input&#8230; Do let me know if you find a way&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Slusser</title>
		<link>http://www.onenaught.com/posts/56/xslt-profilers/comment-page-1#comment-13979</link>
		<dc:creator>Aaron Slusser</dc:creator>
		<pubDate>Tue, 11 Aug 2009 17:47:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/56/xslt-profilers#comment-13979</guid>
		<description>I am trying to profile my xslt, and I don&#039;t use an xml file as input. I use extension objects to pass all the data into the xslt file.

i use the transform function from the XslCompiledTransform type. Is there any way to run the profiler without an input file, just from my code that calls transform.</description>
		<content:encoded><![CDATA[<p>I am trying to profile my xslt, and I don&#8217;t use an xml file as input. I use extension objects to pass all the data into the xslt file.</p>
<p>i use the transform function from the XslCompiledTransform type. Is there any way to run the profiler without an input file, just from my code that calls transform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anup Shah</title>
		<link>http://www.onenaught.com/posts/56/xslt-profilers/comment-page-1#comment-3126</link>
		<dc:creator>Anup Shah</dc:creator>
		<pubDate>Mon, 18 Feb 2008 09:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/56/xslt-profilers#comment-3126</guid>
		<description>@Miguel: that was a good performance boost! I can imagine when the XSLT is using Extension Objects to call through to the database etc, then the profilers are more useful.

I usually try to see if I can &quot;prepare&quot; the XML for the XSLT so the code that gets the XML may perhaps be able to get the data from the database and merge it somehow with the rest of the XML. (But you need to profile that anyway!)

But I like that use of XSLT.

As an aside, I am hoping to shortly post something about using XSLT in MVC, and although the XSLT itself could be a controller (more like MVTemplate!), I am going to talk about it being used in a view. [There will be a post before that to explain why!]</description>
		<content:encoded><![CDATA[<p>@Miguel: that was a good performance boost! I can imagine when the XSLT is using Extension Objects to call through to the database etc, then the profilers are more useful.</p>
<p>I usually try to see if I can &#8220;prepare&#8221; the XML for the XSLT so the code that gets the XML may perhaps be able to get the data from the database and merge it somehow with the rest of the XML. (But you need to profile that anyway!)</p>
<p>But I like that use of XSLT.</p>
<p>As an aside, I am hoping to shortly post something about using XSLT in MVC, and although the XSLT itself could be a controller (more like MVTemplate!), I am going to talk about it being used in a view. [There will be a post before that to explain why!]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miguel de Melo</title>
		<link>http://www.onenaught.com/posts/56/xslt-profilers/comment-page-1#comment-3109</link>
		<dc:creator>Miguel de Melo</dc:creator>
		<pubDate>Sun, 17 Feb 2008 22:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/56/xslt-profilers#comment-3109</guid>
		<description>My experience with profilers is restricted to IDE tools, oXygen and Stylus Studio, both provide a good graphical representation of code reusability and times used to process each section of the code, as well as good stack reports, and link backs to code.

To be fair I haven&#039;t used them as often as I would like to, but I can remember at least one time where it became a life saver for hundreds of users of a large publishing system. There was nothing wrong with the code but the underlying system was supporting the dynamic access of hundreds of documents from the file system using XSL extensions, just to then only extract the title out of full article documents and build a URL to the page. The XSL profiler identified what part of the XSL framework was causing problems, and just by looking at the graphical report it became immediately apparent exactly what line of code was causing havoc.

We then just captured the title of articles in a database table and from then on instead of opening full XML documents, the XSL Extension returned a nodeset with the titles of articles and their respective URLs. We gained a 500% performance increase for that process.</description>
		<content:encoded><![CDATA[<p>My experience with profilers is restricted to IDE tools, oXygen and Stylus Studio, both provide a good graphical representation of code reusability and times used to process each section of the code, as well as good stack reports, and link backs to code.</p>
<p>To be fair I haven&#8217;t used them as often as I would like to, but I can remember at least one time where it became a life saver for hundreds of users of a large publishing system. There was nothing wrong with the code but the underlying system was supporting the dynamic access of hundreds of documents from the file system using XSL extensions, just to then only extract the title out of full article documents and build a URL to the page. The XSL profiler identified what part of the XSL framework was causing problems, and just by looking at the graphical report it became immediately apparent exactly what line of code was causing havoc.</p>
<p>We then just captured the title of articles in a database table and from then on instead of opening full XML documents, the XSL Extension returned a nodeset with the titles of articles and their respective URLs. We gained a 500% performance increase for that process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
