<?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: Ruby and XML</title>
	<atom:link href="http://people.oregonstate.edu/~reeset/blog/archives/324/feed" rel="self" type="application/rss+xml" />
	<link>http://people.oregonstate.edu/~reeset/blog/archives/324</link>
	<description>On my work (programming, digital libraries, cataloging) and other stuff that perks my interest (family, cycling, etc)</description>
	<lastBuildDate>Wed, 28 Oct 2009 05:56:39 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dilettante&#8217;s Ball &#187; The Soul-sucking vacuum that is EAD</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/324/comment-page-1#comment-17189</link>
		<dc:creator>Dilettante&#8217;s Ball &#187; The Soul-sucking vacuum that is EAD</dc:creator>
		<pubDate>Thu, 21 Dec 2006 04:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/324#comment-17189</guid>
		<description>[...] While poring over the REXML API docs, I noticed that the REXML::Element.each_element method&#8217;s argument was called &#8216;xpath&#8217;. Terry had written about how dreadfully slow XPath queries were with REXML and, as a result, I thought I was avoiding them. When I removed the path arg from the each_element call in one of my methods and just iterated through each child element to see if its name matched, it cut the processing time in half! So, while 12 seconds was certainly no thoroughbred, it was definitely the right track. When I eliminated every xpath in the recursion process, I got it down to about 5 seconds. Add a touch of fragment caching and the natural performance boost of a production vs. development site in rails, and I think we&#8217;ve got a &#8220;good enough for now&#8221; solution. [...]</description>
		<content:encoded><![CDATA[<p>[...] While poring over the REXML API docs, I noticed that the REXML::Element.each_element method&#8217;s argument was called &#8216;xpath&#8217;. Terry had written about how dreadfully slow XPath queries were with REXML and, as a result, I thought I was avoiding them. When I removed the path arg from the each_element call in one of my methods and just iterated through each child element to see if its name matched, it cut the processing time in half! So, while 12 seconds was certainly no thoroughbred, it was definitely the right track. When I eliminated every xpath in the recursion process, I got it down to about 5 seconds. Add a touch of fragment caching and the natural performance boost of a production vs. development site in rails, and I think we&#8217;ve got a &#8220;good enough for now&#8221; solution. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
