<?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: New Architecture and Models</title>
	<atom:link href="http://www.seinit.org/privacy-projects/new-architecture-and-models/feed" rel="self" type="application/rss+xml" />
	<link>http://www.seinit.org/privacy-projects/new-architecture-and-models</link>
	<description>Security &#38; Privacy projects</description>
	<lastBuildDate>Sat, 06 Mar 2010 23:08:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Daniel Tunkelang</title>
		<link>http://www.seinit.org/privacy-projects/new-architecture-and-models/comment-page-1#comment-57</link>
		<dc:creator>Daniel Tunkelang</dc:creator>
		<pubDate>Sat, 06 Mar 2010 22:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://seinit.org/?p=39#comment-57</guid>
		<description>I agree that it&#039;s silly to use a complex caching architecture when the main concern is i/o and everything can be fit into an in-memory index / database. My concern here is that some of LinkedIn&#039;s queries sounds CPU-intensive, or at least require lots of random access. I have over 400k degree-two connections, and I&#039;m sure lots of people have more. Sounds like something you don&#039;t want to recompute on every query--but you do have to keep it somewhat up to date as the network changes.</description>
		<content:encoded><![CDATA[<p>I agree that it&#8217;s silly to use a complex caching architecture when the main concern is i/o and everything can be fit into an in-memory index / database. My concern here is that some of LinkedIn&#8217;s queries sounds CPU-intensive, or at least require lots of random access. I have over 400k degree-two connections, and I&#8217;m sure lots of people have more. Sounds like something you don&#8217;t want to recompute on every query&#8211;but you do have to keep it somewhat up to date as the network changes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
