<?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"
	>
<channel>
	<title>Comments on: Will database compression change the hardware game?</title>
	<atom:link href="http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Fri, 25 Jul 2008 01:36:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Zizaco</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-50823</link>
		<dc:creator>Zizaco</dc:creator>
		<pubDate>Wed, 29 Aug 2007 13:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-50823</guid>
		<description>That increase will be very good for games...
Maybe late but it will</description>
		<content:encoded><![CDATA[<p>That increase will be very good for games&#8230;<br />
Maybe late but it will</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On Seaside and State - Cataga</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23176</link>
		<dc:creator>On Seaside and State - Cataga</dc:creator>
		<pubDate>Tue, 27 Mar 2007 02:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23176</guid>
		<description>[...] While I love this work I always seem to come away with a couple of nagging issues. One being the amount of memory required to store state on the server for many requests, which over time will become less of an issue. [...]</description>
		<content:encoded><![CDATA[<p>[...] While I love this work I always seem to come away with a couple of nagging issues. One being the amount of memory required to store state on the server for many requests, which over time will become less of an issue. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Jakosky</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23095</link>
		<dc:creator>Jay Jakosky</dc:creator>
		<pubDate>Mon, 26 Mar 2007 08:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23095</guid>
		<description>I have used QlikView for almost 6 years now and the compression is unbelievable. I routinely get over 20x compression and average 1-2 bytes per field value.</description>
		<content:encoded><![CDATA[<p>I have used QlikView for almost 6 years now and the compression is unbelievable. I routinely get over 20x compression and average 1-2 bytes per field value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kanter</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23069</link>
		<dc:creator>David Kanter</dc:creator>
		<pubDate>Sun, 25 Mar 2007 22:58:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23069</guid>
		<description>So, I believe that the throughput/bandwidth aspect of solid state memory is here to stay for a while.  Just to satisfy our mathematical curiousity, here's are some stats on flash drives:
http://www.bitmicro.com/products_storage_devices.php

Most of them look like they provide up to 70MB/s - half the bandwidth of a 15K RPM drive, but ridiculous numbers of IOPs.  Most disks top out at 150 IOPS, these provide up to 10x that.

The other side of the equation is the tolerance for writes.  While flash memory will never be up to par for heavy write workloads, it's possible that future types of solid state memory could deal with 10x more writes.  That might be sufficient to deal with many transactional workloads.

Also, it's probably good to keep in mind that the MTTF numbers that disk vendors provide are likely not very accurate.  I think it would be interesting to compare the TTF for a set of solid state and traditional disk drives.

DK</description>
		<content:encoded><![CDATA[<p>So, I believe that the throughput/bandwidth aspect of solid state memory is here to stay for a while.  Just to satisfy our mathematical curiousity, here&#8217;s are some stats on flash drives:<br />
<a href="http://www.bitmicro.com/products_storage_devices.php" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.bitmicro.com');" rel="nofollow">http://www.bitmicro.com/products_storage_devices.php</a></p>
<p>Most of them look like they provide up to 70MB/s - half the bandwidth of a 15K RPM drive, but ridiculous numbers of IOPs.  Most disks top out at 150 IOPS, these provide up to 10x that.</p>
<p>The other side of the equation is the tolerance for writes.  While flash memory will never be up to par for heavy write workloads, it&#8217;s possible that future types of solid state memory could deal with 10x more writes.  That might be sufficient to deal with many transactional workloads.</p>
<p>Also, it&#8217;s probably good to keep in mind that the MTTF numbers that disk vendors provide are likely not very accurate.  I think it would be interesting to compare the TTF for a set of solid state and traditional disk drives.</p>
<p>DK</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23007</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sun, 25 Mar 2007 14:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-23007</guid>
		<description>Thanks, David!

But is that a locked-in aspect of the technology, or can we expect it to improve over time?</description>
		<content:encoded><![CDATA[<p>Thanks, David!</p>
<p>But is that a locked-in aspect of the technology, or can we expect it to improve over time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kanter</title>
		<link>http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-22929</link>
		<dc:creator>David Kanter</dc:creator>
		<pubDate>Sun, 25 Mar 2007 00:38:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/24/will-data-compression-change-the-hardware-game/#comment-22929</guid>
		<description>Hi Curt,

Just a quick comment regarding flash.

Flash doesn't actually support the bandwidth required for data-warehousing.  While flash can support orders of magnitude more IOPS than disk, the bandwidth of each IOP is fairly small.  The bandwidth provided is basically (size of read)*(number of IOPS).  In comparison, disks provide few IOPS, but under the right circumstances, the read bandwidth becomes very very large.  
Most flash devices are not going to get any where close to the 70-100MB/s that a disk can achieve (reading data that has high spatial locality).  This means flash is largely unsuitable for the underlying data in a warehouse.

Flash makes sense for OLTP (actually Texas Memory Systems has devices targeted specifically at OLTP).  The only issue there is that many frequent reads will eventually wear down the flash...if you're sustaining thousands of writes/sec, it may prove to be an unwise choice.

DK</description>
		<content:encoded><![CDATA[<p>Hi Curt,</p>
<p>Just a quick comment regarding flash.</p>
<p>Flash doesn&#8217;t actually support the bandwidth required for data-warehousing.  While flash can support orders of magnitude more IOPS than disk, the bandwidth of each IOP is fairly small.  The bandwidth provided is basically (size of read)*(number of IOPS).  In comparison, disks provide few IOPS, but under the right circumstances, the read bandwidth becomes very very large.<br />
Most flash devices are not going to get any where close to the 70-100MB/s that a disk can achieve (reading data that has high spatial locality).  This means flash is largely unsuitable for the underlying data in a warehouse.</p>
<p>Flash makes sense for OLTP (actually Texas Memory Systems has devices targeted specifically at OLTP).  The only issue there is that many frequent reads will eventually wear down the flash&#8230;if you&#8217;re sustaining thousands of writes/sec, it may prove to be an unwise choice.</p>
<p>DK</p>
]]></content:encoded>
	</item>
</channel>
</rss>
