<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Search Engine Speedups</title>
	<atom:link href="http://bluebloomer.wordpress.com/2009/07/02/search-engine-speedups/feed/" rel="self" type="application/rss+xml" />
	<link>http://bluebloomer.wordpress.com/2009/07/02/search-engine-speedups/</link>
	<description>Bluebloomer - Not a pair of pants</description>
	<lastBuildDate>Thu, 02 Jul 2009 14:23:16 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bluebloomer</title>
		<link>http://bluebloomer.wordpress.com/2009/07/02/search-engine-speedups/#comment-8</link>
		<dc:creator>bluebloomer</dc:creator>
		<pubDate>Thu, 02 Jul 2009 14:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://bluebloomer.wordpress.com/?p=64#comment-8</guid>
		<description>An update on this. So far I have not implemented caching or sacrificed accuracy, and the speed is still really good with the above method.

I did something a bit unconventional. I opted to process some of the query in PHP. This has also given a good speed boost because I&#039;m able to use a few tricks in joining data. The result is something which actually works with ridiculous improvements on what I had before.</description>
		<content:encoded><![CDATA[<p>An update on this. So far I have not implemented caching or sacrificed accuracy, and the speed is still really good with the above method.</p>
<p>I did something a bit unconventional. I opted to process some of the query in PHP. This has also given a good speed boost because I&#8217;m able to use a few tricks in joining data. The result is something which actually works with ridiculous improvements on what I had before.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
