<?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: FusionIO</title>
	<atom:link href="http://blog.50micron.com/2008/04/23/fusionio/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.50micron.com/2008/04/23/fusionio/</link>
	<description>Ranting and raving about storage and technology</description>
	<lastBuildDate>Mon, 19 Dec 2011 15:36:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: SanGod</title>
		<link>http://blog.50micron.com/2008/04/23/fusionio/comment-page-1/#comment-6213</link>
		<dc:creator>SanGod</dc:creator>
		<pubDate>Tue, 06 May 2008 03:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=212#comment-6213</guid>
		<description>Yeah - My only real question of course is whether they have fond a way around the 100,000 write-erase-cycle limit for NAND flash memory.

Most flash-based systems use something called write-levelling, which is largely a way of randomizing IO (in flash memory, random IO is not a performance problem like it is in hard-drives) so that each block gets eat an equal amount of time.

NAND flash memory has a limited number of write-erase cycles, around 100,000 under current design.  Now a write-erase only occurs when the blocks need to be set to zero.  IE you can change 0000 to 0001 to 0011 to 0111 to 1111 without going through an erase cycle, (or any combination thereof) however in order to change any bit from 1 to 0 requires that that entire block be erased and re-written.  This could prove to be a substantial limitation for the type of storage.

That being said, it&#039;s just as much a limitation for every type of NAND-Flash based storage.  If Fusion-IO has come up with a solid write-levelling algorithm and can truly distribute the Io across the entire card, then they by far have the superior product.  

As I understand it, most commercially available SSD disks write as a normal disk, which could cause them to run up against that write-erase barrier much sooner.  (IE if a disk is 30% full, the first 30% of the drive is most active and will hit the limit far before the end of the address-space.

Assuming of course that the SSD manufacturers haven&#039;t already adjusted to this with a write-levelling algorithm of their own.</description>
		<content:encoded><![CDATA[<p>Yeah &#8211; My only real question of course is whether they have fond a way around the 100,000 write-erase-cycle limit for NAND flash memory.</p>
<p>Most flash-based systems use something called write-levelling, which is largely a way of randomizing IO (in flash memory, random IO is not a performance problem like it is in hard-drives) so that each block gets eat an equal amount of time.</p>
<p>NAND flash memory has a limited number of write-erase cycles, around 100,000 under current design.  Now a write-erase only occurs when the blocks need to be set to zero.  IE you can change 0000 to 0001 to 0011 to 0111 to 1111 without going through an erase cycle, (or any combination thereof) however in order to change any bit from 1 to 0 requires that that entire block be erased and re-written.  This could prove to be a substantial limitation for the type of storage.</p>
<p>That being said, it&#8217;s just as much a limitation for every type of NAND-Flash based storage.  If Fusion-IO has come up with a solid write-levelling algorithm and can truly distribute the Io across the entire card, then they by far have the superior product.  </p>
<p>As I understand it, most commercially available SSD disks write as a normal disk, which could cause them to run up against that write-erase barrier much sooner.  (IE if a disk is 30% full, the first 30% of the drive is most active and will hit the limit far before the end of the address-space.</p>
<p>Assuming of course that the SSD manufacturers haven&#8217;t already adjusted to this with a write-levelling algorithm of their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://blog.50micron.com/2008/04/23/fusionio/comment-page-1/#comment-6196</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Tue, 29 Apr 2008 23:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=212#comment-6196</guid>
		<description>Yes, yes I have.  This was the first question I brought up when everyone was ranting and raving about the flash disks in EMC&#039;s arrays for those one or two database servers that need maximal performance.  This will kick the crap out of that any day of the week.</description>
		<content:encoded><![CDATA[<p>Yes, yes I have.  This was the first question I brought up when everyone was ranting and raving about the flash disks in EMC&#8217;s arrays for those one or two database servers that need maximal performance.  This will kick the crap out of that any day of the week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SanGod</title>
		<link>http://blog.50micron.com/2008/04/23/fusionio/comment-page-1/#comment-6195</link>
		<dc:creator>SanGod</dc:creator>
		<pubDate>Thu, 24 Apr 2008 15:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=212#comment-6195</guid>
		<description>yeah - the funny part is - I run Vista on my PC at home, with moderate success, of course I have as my disk back-end right now a 4-drive Raid-1/0 set so there is a certain amount of performance benefit there.  I can still watch the harddrive thrash when i do something overly complicated----like logging in.

This would end that struggle once and for all. ;-)  probably a 15 second boot time. :)</description>
		<content:encoded><![CDATA[<p>yeah &#8211; the funny part is &#8211; I run Vista on my PC at home, with moderate success, of course I have as my disk back-end right now a 4-drive Raid-1/0 set so there is a certain amount of performance benefit there.  I can still watch the harddrive thrash when i do something overly complicated&#8212;-like logging in.</p>
<p>This would end that struggle once and for all. <img src='http://blog.50micron.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />   probably a 15 second boot time. <img src='http://blog.50micron.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: athgeek</title>
		<link>http://blog.50micron.com/2008/04/23/fusionio/comment-page-1/#comment-6194</link>
		<dc:creator>athgeek</dc:creator>
		<pubDate>Thu, 24 Apr 2008 05:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sangod.com/?p=212#comment-6194</guid>
		<description>Saw them at SNW in Orlando a little while ago.  Had three ioDrives running on a gaming machine; not sure what capacity; I believe it was a software RAID.  Showed 2+GBs per second streaming, and well over 200,000 IOPS.  Amazing.  Also, each ioDrive only consumes 6 watts, so an extremely GREEN device.  I want one!!!</description>
		<content:encoded><![CDATA[<p>Saw them at SNW in Orlando a little while ago.  Had three ioDrives running on a gaming machine; not sure what capacity; I believe it was a software RAID.  Showed 2+GBs per second streaming, and well over 200,000 IOPS.  Amazing.  Also, each ioDrive only consumes 6 watts, so an extremely GREEN device.  I want one!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

