<?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: Google File Systems v2, part 1</title>
	<atom:link href="http://storagemojo.com/2009/08/17/google-file-systems-v2-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com/2009/08/17/google-file-systems-v2-part-1/</link>
	<description>Data storage info &#38; analysis</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:02:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Google搜索新索引Caffeine分析 - 易IT博客</title>
		<link>http://storagemojo.com/2009/08/17/google-file-systems-v2-part-1/comment-page-1/#comment-210080</link>
		<dc:creator>Google搜索新索引Caffeine分析 - 易IT博客</dc:creator>
		<pubDate>Tue, 13 Jul 2010 17:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1533#comment-210080</guid>
		<description>[...] 搜索引擎索引系统架构的更新: Google文件系统从GFS v1(Google File System)升级到GFS v2 [...]</description>
		<content:encoded><![CDATA[<p>[...] 搜索引擎索引系统架构的更新: Google文件系统从GFS v1(Google File System)升级到GFS v2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Pearson</title>
		<link>http://storagemojo.com/2009/08/17/google-file-systems-v2-part-1/comment-page-1/#comment-205046</link>
		<dc:creator>Robert Pearson</dc:creator>
		<pubDate>Thu, 10 Sep 2009 13:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=1533#comment-205046</guid>
		<description>These are two of your finest posts.

&quot;Google File System v2, part 1&quot;
&quot;Google File System v2, part 2&quot;

To my regret these articulate, salient posts went unanswered.
This tells me that the level of &quot;Storage Problem Solving&quot; is still an
art and may never be a science.

The original problem of &quot;Access Density&quot; was tied specifically to disk drives.
Your two posts highlight where the coming &quot;Access Density&quot; problem
will be joined.
When I started looking at bandwidth needs for &quot;End-to-End Information
on Demand (E2EIoD)&quot; there were many other areas (bottlenecks, hot spots) for
restricting or impeding the flow of Information. I tried to identify the most important ones with the &quot;Speed Limit of the Information Universe&quot; concept. 

To deal with the problem of the &quot;fire fighting&quot; IT mentality for bottlenecks and hotspots with $pounds and $pounds of $cure, an ounce of prevention would be cheaper and work better. The ounce of prevention would be to have Infrastructure Bandwidth costs added as a line item in the IT budget.
Two options:
1) How much bandwidth do you need? How much can you afford?
2) How much can you afford? How much do you need?</description>
		<content:encoded><![CDATA[<p>These are two of your finest posts.</p>
<p>&#8220;Google File System v2, part 1&#8243;<br />
&#8220;Google File System v2, part 2&#8243;</p>
<p>To my regret these articulate, salient posts went unanswered.<br />
This tells me that the level of &#8220;Storage Problem Solving&#8221; is still an<br />
art and may never be a science.</p>
<p>The original problem of &#8220;Access Density&#8221; was tied specifically to disk drives.<br />
Your two posts highlight where the coming &#8220;Access Density&#8221; problem<br />
will be joined.<br />
When I started looking at bandwidth needs for &#8220;End-to-End Information<br />
on Demand (E2EIoD)&#8221; there were many other areas (bottlenecks, hot spots) for<br />
restricting or impeding the flow of Information. I tried to identify the most important ones with the &#8220;Speed Limit of the Information Universe&#8221; concept. </p>
<p>To deal with the problem of the &#8220;fire fighting&#8221; IT mentality for bottlenecks and hotspots with $pounds and $pounds of $cure, an ounce of prevention would be cheaper and work better. The ounce of prevention would be to have Infrastructure Bandwidth costs added as a line item in the IT budget.<br />
Two options:<br />
1) How much bandwidth do you need? How much can you afford?<br />
2) How much can you afford? How much do you need?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

