<?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: Handling a huge amount of fulltext searches</title>
	<atom:link href="http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/</link>
	<description>Where the rising ape meets the falling angel</description>
	<lastBuildDate>Thu, 01 Dec 2011 08:19:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: J. Digle</title>
		<link>http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/#comment-5</link>
		<dc:creator>J. Digle</dc:creator>
		<pubDate>Thu, 28 May 2009 06:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.iamnolegend.com/?p=3#comment-5</guid>
		<description>Try SOLR.</description>
		<content:encoded><![CDATA[<p>Try SOLR.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ochronus</title>
		<link>http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/#comment-4</link>
		<dc:creator>ochronus</dc:creator>
		<pubDate>Fri, 22 May 2009 20:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.iamnolegend.com/?p=3#comment-4</guid>
		<description>&lt;a href=&quot;#comment-1346&quot; rel=&quot;nofollow&quot;&gt;@John Haugeland&lt;/a&gt; 
Generally speaking, you&#039;re absolutely right, but consider development time. In about two hours I managed to put together a system which handles around 120 req/s with a concurrency of 50 on low-grade hardware. Of course I&#039;m not talking about facebook or twitter size load :)</description>
		<content:encoded><![CDATA[<p><a href="#comment-1346" rel="nofollow">@John Haugeland</a><br />
Generally speaking, you&#8217;re absolutely right, but consider development time. In about two hours I managed to put together a system which handles around 120 req/s with a concurrency of 50 on low-grade hardware. Of course I&#8217;m not talking about facebook or twitter size load <img src='http://blog.mostof.it/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Haugeland</title>
		<link>http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/#comment-3</link>
		<dc:creator>John Haugeland</dc:creator>
		<pubDate>Fri, 22 May 2009 19:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.iamnolegend.com/?p=3#comment-3</guid>
		<description>Generally speaking, the appropriate answer for something like this is a compiled language with efficient machine-near datastructures, such as C++ or Forth, since then you can just multihash the words and keep a large bucket histograph.  If you&#039;re trying to handle a &quot;huge&quot; amount of searches, you shouldn&#039;t be stubbing yourself by working with general-case tools.

You&#039;re likely to see two orders of magnitude improvement with a well chosen string hash and a non-generalized hash table.  The C++ unordered_multimap in Boost is almost certainly what you&#039;re looking for.</description>
		<content:encoded><![CDATA[<p>Generally speaking, the appropriate answer for something like this is a compiled language with efficient machine-near datastructures, such as C++ or Forth, since then you can just multihash the words and keep a large bucket histograph.  If you&#8217;re trying to handle a &#8220;huge&#8221; amount of searches, you shouldn&#8217;t be stubbing yourself by working with general-case tools.</p>
<p>You&#8217;re likely to see two orders of magnitude improvement with a well chosen string hash and a non-generalized hash table.  The C++ unordered_multimap in Boost is almost certainly what you&#8217;re looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Handling a huge amount of fulltext searches part 2 - the internals &#124; blog@iamnolegend.com</title>
		<link>http://blog.mostof.it/handling-a-huge-amount-of-fulltext-searches/#comment-2</link>
		<dc:creator>Handling a huge amount of fulltext searches part 2 - the internals &#124; blog@iamnolegend.com</dc:creator>
		<pubDate>Sat, 07 Feb 2009 06:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.iamnolegend.com/?p=3#comment-2</guid>
		<description>[...] In part one, I generally drafted the ingredients needed for the system, now it’s time to have a deeper look at the internal workings, processes and connections. [...] </description>
		<content:encoded><![CDATA[<p>[...] In part one, I generally drafted the ingredients needed for the system, now it’s time to have a deeper look at the internal workings, processes and connections. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

