<?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: Brian Aker: 20GB doesn&#8217;t fit on a single server</title>
	<atom:link href="http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/</link>
	<description>Stay curious!</description>
	<lastBuildDate>Thu, 09 Feb 2012 09:56:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Robert Treat</title>
		<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/#comment-18151</link>
		<dc:creator>Robert Treat</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1725#comment-18151</guid>
		<description>Just a counter point, we have servers running postgres on boxes with 32 cores and 512GB of ram. From our experience, it scales pretty well on that size hardware; by far our largest problems are (still) disk related. Now, if your argument is that you could scale so much better on Oracle on that kind of hardware, I&#039;m not going to argue that point, but Postgres on that kind of hardware would do the job for 99% of the people out there.</description>
		<content:encoded><![CDATA[<p>Just a counter point, we have servers running postgres on boxes with 32 cores and 512GB of ram. From our experience, it scales pretty well on that size hardware; by far our largest problems are (still) disk related. Now, if your argument is that you could scale so much better on Oracle on that kind of hardware, I&#8217;m not going to argue that point, but Postgres on that kind of hardware would do the job for 99% of the people out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/#comment-18140</link>
		<dc:creator>William</dc:creator>
		<pubDate>Mon, 12 Apr 2010 17:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1725#comment-18140</guid>
		<description>I agree with Barron. I had to re-read that article a few times.  Its pretty clear to me that it implies Brian doesn&#039;t think it can handle 20 GB. I was left to conclude that the author misquoted/misrepresented what he was saying, or there is an interesting use case ( maybe heavy write /update use case) where even 20 GB doesn&#039;t work on a single box.</description>
		<content:encoded><![CDATA[<p>I agree with Barron. I had to re-read that article a few times.  Its pretty clear to me that it implies Brian doesn&#8217;t think it can handle 20 GB. I was left to conclude that the author misquoted/misrepresented what he was saying, or there is an interesting use case ( maybe heavy write /update use case) where even 20 GB doesn&#8217;t work on a single box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/#comment-18138</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Mon, 12 Apr 2010 14:12:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1725#comment-18138</guid>
		<description>A few years ago, I came up with an idea here at work, and led a team of 3 (myself included) to develop a distributed processing system in SQL Server.  From design to implementation was 9 months.  It&#039;s currently one of our most important systems.  We get about 6 million new records per day, and run about 300 SQL statements on each of them on average.  I looked into existing solutions like Map Reduce, and found that for what most database systems need, they aren&#039;t well suited.  I&#039;ll qualify that by stating that they weren&#039;t well suited based on my understanding of them.

Our processing requirements required doing lookups on many other tables, both small and large.  We weren&#039;t lucky enough to do simple aggregates (this word is on that webpage 9 times).  A lot of the lookups are slightly complex (get the newest lookup record that was in place on this date at this time, etc.).

I would agree that 20G of data isn&#039;t nearly enough to require distributing it, unless you are expecting explosive growth in the near future.  The worst time to switch do a larger/better solution is when you &quot;need&quot; do.  I&#039;d always prefer doing that ahead of the data flood when possible.</description>
		<content:encoded><![CDATA[<p>A few years ago, I came up with an idea here at work, and led a team of 3 (myself included) to develop a distributed processing system in SQL Server.  From design to implementation was 9 months.  It&#8217;s currently one of our most important systems.  We get about 6 million new records per day, and run about 300 SQL statements on each of them on average.  I looked into existing solutions like Map Reduce, and found that for what most database systems need, they aren&#8217;t well suited.  I&#8217;ll qualify that by stating that they weren&#8217;t well suited based on my understanding of them.</p>
<p>Our processing requirements required doing lookups on many other tables, both small and large.  We weren&#8217;t lucky enough to do simple aggregates (this word is on that webpage 9 times).  A lot of the lookups are slightly complex (get the newest lookup record that was in place on this date at this time, etc.).</p>
<p>I would agree that 20G of data isn&#8217;t nearly enough to require distributing it, unless you are expecting explosive growth in the near future.  The worst time to switch do a larger/better solution is when you &#8220;need&#8221; do.  I&#8217;d always prefer doing that ahead of the data flood when possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/#comment-18137</link>
		<dc:creator>Xaprb</dc:creator>
		<pubDate>Sun, 11 Apr 2010 18:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1725#comment-18137</guid>
		<description>PS, note: I know Brian is smart, and knows that 20gb fits onto a computer, which is why I said the interview &quot;quoted him as saying&quot; instead of directly attributing it to him :-)</description>
		<content:encoded><![CDATA[<p>PS, note: I know Brian is smart, and knows that 20gb fits onto a computer, which is why I said the interview &#8220;quoted him as saying&#8221; instead of directly attributing it to him :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Pipes</title>
		<link>http://www.xaprb.com/blog/2010/04/10/brian-aker-20gb-doesnt-fit-on-a-single-server/#comment-18136</link>
		<dc:creator>Jay Pipes</dc:creator>
		<pubDate>Sun, 11 Apr 2010 18:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1725#comment-18136</guid>
		<description>see you soon :)

/me goes off to hit the weights for the cage match.</description>
		<content:encoded><![CDATA[<p>see you soon :)</p>
<p>/me goes off to hit the weights for the cage match.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

