<?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: Our changing file workloads</title>
	<atom:link href="http://storagemojo.com/2008/09/09/our-changing-file-workloads/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/</link>
	<description>Data storage info &#38; analysis</description>
	<lastBuildDate>Sun, 20 May 2012 13:26:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Build a 135TB array for $7,384 &#124; ZDNet</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-217734</link>
		<dc:creator>Build a 135TB array for $7,384 &#124; ZDNet</dc:creator>
		<pubDate>Wed, 20 Jul 2011 14:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-217734</guid>
		<description>[...] peoples of the world gift by open-sourcing their storage pod design. Most business files are opened only a few times, so why put them on the most costly storage you can [...]</description>
		<content:encoded><![CDATA[<p>[...] peoples of the world gift by open-sourcing their storage pod design. Most business files are opened only a few times, so why put them on the most costly storage you can [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dell TechCenter</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-202316</link>
		<dc:creator>Dell TechCenter</dc:creator>
		<pubDate>Fri, 29 May 2009 19:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-202316</guid>
		<description>&lt;strong&gt;How Well Do You Know Your Data?...&lt;/strong&gt;

If you are sensing a pattern to some of my blogs, you are probably correct. One of the reasons I write...</description>
		<content:encoded><![CDATA[<p><strong>How Well Do You Know Your Data?&#8230;</strong></p>
<p>If you are sensing a pattern to some of my blogs, you are probably correct. One of the reasons I write&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HPCC</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-200355</link>
		<dc:creator>HPCC</dc:creator>
		<pubDate>Wed, 15 Apr 2009 13:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-200355</guid>
		<description>&lt;strong&gt;How Well Do You Know Your Data?...&lt;/strong&gt;

If you are sensing a pattern to some of my blogs, you are probably correct. One of the reasons I write...</description>
		<content:encoded><![CDATA[<p><strong>How Well Do You Know Your Data?&#8230;</strong></p>
<p>If you are sensing a pattern to some of my blogs, you are probably correct. One of the reasons I write&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bobby Moulton</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-198008</link>
		<dc:creator>Bobby Moulton</dc:creator>
		<pubDate>Thu, 16 Oct 2008 16:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-198008</guid>
		<description>Good article Robin - 

This data is important.  This is the kind of information our company - Seven10 - has used to promote a data management paradigm change.  And while I think you are almost there in your view of how data should be managed, I still think you are putting too much emphasis on migration.

Data placement across tiers with retention policies is the key.

Take a look at our EAS product - tiered storage offering support for disk, cas, and tape (as an archive) and I think you will see that there is a better approach to managing the growth of fixed content.  

We see an end of days for back-up as an archive - it simply is too costly to manage.

I look forward to hearing from you.

Bobby Moulton
President
Seven10
bmoulton@seventenstorage.com</description>
		<content:encoded><![CDATA[<p>Good article Robin &#8211; </p>
<p>This data is important.  This is the kind of information our company &#8211; Seven10 &#8211; has used to promote a data management paradigm change.  And while I think you are almost there in your view of how data should be managed, I still think you are putting too much emphasis on migration.</p>
<p>Data placement across tiers with retention policies is the key.</p>
<p>Take a look at our EAS product &#8211; tiered storage offering support for disk, cas, and tape (as an archive) and I think you will see that there is a better approach to managing the growth of fixed content.  </p>
<p>We see an end of days for back-up as an archive &#8211; it simply is too costly to manage.</p>
<p>I look forward to hearing from you.</p>
<p>Bobby Moulton<br />
President<br />
Seven10<br />
<a href="mailto:bmoulton@seventenstorage.com">bmoulton@seventenstorage.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197877</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 01 Oct 2008 22:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197877</guid>
		<description>Why not virtualize the NAS? Utilize the workflow, data to a degree that can use the all the storage capacity, resources available. Product like Acopia for taking advantage of the NetApp, EMC, and Network Attached Storage.

That would be a better way.</description>
		<content:encoded><![CDATA[<p>Why not virtualize the NAS? Utilize the workflow, data to a degree that can use the all the storage capacity, resources available. Product like Acopia for taking advantage of the NetApp, EMC, and Network Attached Storage.</p>
<p>That would be a better way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cinetica Blog &#187; Troppo BELLO per essere VERO !!!</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197709</link>
		<dc:creator>Cinetica Blog &#187; Troppo BELLO per essere VERO !!!</dc:creator>
		<pubDate>Mon, 22 Sep 2008 14:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197709</guid>
		<description>[...] riduce i costi dello storage: uno studio pubblicato da poco e ripreso anche su StorageMojo dimostra che l&#8217;80% dei dati che avete nei vostri storage è inattivo!!!! con Compellent [...]</description>
		<content:encoded><![CDATA[<p>[...] riduce i costi dello storage: uno studio pubblicato da poco e ripreso anche su StorageMojo dimostra che l&#8217;80% dei dati che avete nei vostri storage è inattivo!!!! con Compellent [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin G</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197597</link>
		<dc:creator>Martin G</dc:creator>
		<pubDate>Tue, 16 Sep 2008 15:11:19 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197597</guid>
		<description>The 76% of files only accessed by a single user, makes you wonder why we provide shared file-systems for most users. There&#039;s got to be a better way of doing this.</description>
		<content:encoded><![CDATA[<p>The 76% of files only accessed by a single user, makes you wonder why we provide shared file-systems for most users. There&#8217;s got to be a better way of doing this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Jones</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197535</link>
		<dc:creator>Steve Jones</dc:creator>
		<pubDate>Fri, 12 Sep 2008 12:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197535</guid>
		<description>There&#039;s no major surprises here. As the available storage capacity for a given amount of money increases on an exponential curve, then the tendency will be to store more and more low-access, low-value data. The costs of managing this storage (by the individual creating it) do not so decline - or at least without automation. 
Measured another way, it&#039;s just as well that the access frequency of storage is on the decline. The rate of increase of I/O throughput bandwidth and IOPs are on much lower curves (especially the latter). Quite simply, if the access density per GB of today&#039;s data looked anything like it did a decade ago then the storage systems would be unusable.</description>
		<content:encoded><![CDATA[<p>There&#8217;s no major surprises here. As the available storage capacity for a given amount of money increases on an exponential curve, then the tendency will be to store more and more low-access, low-value data. The costs of managing this storage (by the individual creating it) do not so decline &#8211; or at least without automation.<br />
Measured another way, it&#8217;s just as well that the access frequency of storage is on the decline. The rate of increase of I/O throughput bandwidth and IOPs are on much lower curves (especially the latter). Quite simply, if the access density per GB of today&#8217;s data looked anything like it did a decade ago then the storage systems would be unusable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jered Floyd</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197531</link>
		<dc:creator>Jered Floyd</dc:creator>
		<pubDate>Thu, 11 Sep 2008 22:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197531</guid>
		<description>Robin,

I saw this paper, and while I appreciate the data, I find it unfruitful for drawing conclusions.  The particular customer involved appears to make extraordinarily little use of their storage.   Their needs could likely be met with a 386 running Linux running with drives from the same era. 

I&#039;d really like to see aggregate data from a wide variety of  customers, and I hope the authors will go on to do so.   I&#039;ll say for a fact that zero of the conclusions you can draw from that report apply to our development file server, and I bet that&#039;s likely true for many others!

Regards,
Jered Floyd
CTO, Permabit Technology Corp.</description>
		<content:encoded><![CDATA[<p>Robin,</p>
<p>I saw this paper, and while I appreciate the data, I find it unfruitful for drawing conclusions.  The particular customer involved appears to make extraordinarily little use of their storage.   Their needs could likely be met with a 386 running Linux running with drives from the same era. </p>
<p>I&#8217;d really like to see aggregate data from a wide variety of  customers, and I hope the authors will go on to do so.   I&#8217;ll say for a fact that zero of the conclusions you can draw from that report apply to our development file server, and I bet that&#8217;s likely true for many others!</p>
<p>Regards,<br />
Jered Floyd<br />
CTO, Permabit Technology Corp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Malayter</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197526</link>
		<dc:creator>Ryan Malayter</dc:creator>
		<pubDate>Thu, 11 Sep 2008 13:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197526</guid>
		<description>Funny, we just did a similar study last year internally on all of our storage, including DB and mail servers. The results were startingly similar. 2:1 read:write ratio, 12 KB average IO size, and very few files are ever touched beyond 30 days of creation.

That said, I do not think a study of two NAS installations is statistacilly significant. WHat is really needed is a long-term study of hundreds of disparate organizations. Something only a vendor could do, I suppose, with remote monitoring and opt-in from customers.

Also, the fact that such studies are &quot;blind&quot; to access patterns inside datbases and virtual machine files is also quite a flaw.</description>
		<content:encoded><![CDATA[<p>Funny, we just did a similar study last year internally on all of our storage, including DB and mail servers. The results were startingly similar. 2:1 read:write ratio, 12 KB average IO size, and very few files are ever touched beyond 30 days of creation.</p>
<p>That said, I do not think a study of two NAS installations is statistacilly significant. WHat is really needed is a long-term study of hundreds of disparate organizations. Something only a vendor could do, I suppose, with remote monitoring and opt-in from customers.</p>
<p>Also, the fact that such studies are &#8220;blind&#8221; to access patterns inside datbases and virtual machine files is also quite a flaw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ernst Lopes Cardozo</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197520</link>
		<dc:creator>Ernst Lopes Cardozo</dc:creator>
		<pubDate>Wed, 10 Sep 2008 21:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197520</guid>
		<description>To me these observation suggest a different policy: write new files to backup storage first, then copy to primary storage when requested. Primary storage becomes a cache that does not need backup. Effectively, the backup process is spread over the day. Motivation: all new files need to be backuped, but only a fraction will be accessed. Backup is to disk and needs to be replicated to disk or tape at a DR site. The capacity of primary storage becomes flexible, there will be no &#039;disk full&#039; conditions, only sub-optimal performance when the primary storage (the cache) is too small.</description>
		<content:encoded><![CDATA[<p>To me these observation suggest a different policy: write new files to backup storage first, then copy to primary storage when requested. Primary storage becomes a cache that does not need backup. Effectively, the backup process is spread over the day. Motivation: all new files need to be backuped, but only a fraction will be accessed. Backup is to disk and needs to be replicated to disk or tape at a DR site. The capacity of primary storage becomes flexible, there will be no &#8216;disk full&#8217; conditions, only sub-optimal performance when the primary storage (the cache) is too small.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Emery</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197516</link>
		<dc:creator>Matthew Emery</dc:creator>
		<pubDate>Wed, 10 Sep 2008 13:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197516</guid>
		<description>Thanks for this, I have found the study interesting.  

One recommendation though has been left out from the end of section 5

&quot;While access to file metadata should
be fast, this indicates much file data can be compressed,
de-duplicated, or placed on low power storage, improving
utilization and power consumption, without significantly
impacting performance. In addition, our observation
that file re-accesses are temporally correlated (see
Section 4.5) means there are opportunities for intelligent
migration scheduling decisions.&quot;

... or data can be deleted.</description>
		<content:encoded><![CDATA[<p>Thanks for this, I have found the study interesting.  </p>
<p>One recommendation though has been left out from the end of section 5</p>
<p>&#8220;While access to file metadata should<br />
be fast, this indicates much file data can be compressed,<br />
de-duplicated, or placed on low power storage, improving<br />
utilization and power consumption, without significantly<br />
impacting performance. In addition, our observation<br />
that file re-accesses are temporally correlated (see<br />
Section 4.5) means there are opportunities for intelligent<br />
migration scheduling decisions.&#8221;</p>
<p>&#8230; or data can be deleted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Todd</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197515</link>
		<dc:creator>Steve Todd</dc:creator>
		<pubDate>Wed, 10 Sep 2008 13:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197515</guid>
		<description>Robin,
Thanks for sharing the pointer to the paper. I find it interesting from an industry and product perspective. The SNIA XAM initiative (www.snia.org/forums/xam) is an industry effort that deals with exactly this issue (managing fixed or unchanging content). At EMC we&#039;re also seeing strong demand for products that silently migrate untouched data, whether it&#039;s performed at the server, in the network, or in the filer.
Steve</description>
		<content:encoded><![CDATA[<p>Robin,<br />
Thanks for sharing the pointer to the paper. I find it interesting from an industry and product perspective. The SNIA XAM initiative (www.snia.org/forums/xam) is an industry effort that deals with exactly this issue (managing fixed or unchanging content). At EMC we&#8217;re also seeing strong demand for products that silently migrate untouched data, whether it&#8217;s performed at the server, in the network, or in the filer.<br />
Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Systems Storage Guy</title>
		<link>http://storagemojo.com/2008/09/09/our-changing-file-workloads/comment-page-1/#comment-197513</link>
		<dc:creator>Open Systems Storage Guy</dc:creator>
		<pubDate>Wed, 10 Sep 2008 12:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=928#comment-197513</guid>
		<description>Interesting data- I wish someone would do this for Oracle, SQL, Exchange, and some other heavy hitting DB applications...</description>
		<content:encoded><![CDATA[<p>Interesting data- I wish someone would do this for Oracle, SQL, Exchange, and some other heavy hitting DB applications&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

