<?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: Netezza’s chip story</title>
	<atom:link href="http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Sun, 20 Jul 2008 01:21:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-54711</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sat, 29 Sep 2007 12:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-54711</guid>
		<description>Hiya.

Lots of clues elsewhere in this blog.  Index-light MPP architectures such as Netezza's or DATAllegro's are waaaay better for large data warehouses than traditional index-heavy SMP systems like Oracle or Microsoft SQL*Server.

More debatable is the choice between FPGAs (Netezza) and more conventional chips (pretty much everybody else).  Both choices have a lot of merit.

CAM</description>
		<content:encoded><![CDATA[<p>Hiya.</p>
<p>Lots of clues elsewhere in this blog.  Index-light MPP architectures such as Netezza&#8217;s or DATAllegro&#8217;s are waaaay better for large data warehouses than traditional index-heavy SMP systems like Oracle or Microsoft SQL*Server.</p>
<p>More debatable is the choice between FPGAs (Netezza) and more conventional chips (pretty much everybody else).  Both choices have a lot of merit.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diskpharma</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-54650</link>
		<dc:creator>diskpharma</dc:creator>
		<pubDate>Sat, 29 Sep 2007 03:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-54650</guid>
		<description>At one of Netezza's User Conference technical breakout sessions this week they basically opened the kimona.
They discussed in great detail with animated slides the technology utilized starting from the user query to
the front end software optimization and scheduling, how the query is distributed &#38; executed on the SPUs, how
data is manipulated, and ultimately sent back to the host and to the user for the answer to their query.

Also several of their customers gave presentations at their business track sessions disclosing their DW
deployment and reported performance gains of 2 and 3 orders of magnitude. So something is missing in the
technical analysis just comparing disk data rates which on average cannot go faster than 70 MB/s. Any clues??</description>
		<content:encoded><![CDATA[<p>At one of Netezza&#8217;s User Conference technical breakout sessions this week they basically opened the kimona.<br />
They discussed in great detail with animated slides the technology utilized starting from the user query to<br />
the front end software optimization and scheduling, how the query is distributed &amp; executed on the SPUs, how<br />
data is manipulated, and ultimately sent back to the host and to the user for the answer to their query.</p>
<p>Also several of their customers gave presentations at their business track sessions disclosing their DW<br />
deployment and reported performance gains of 2 and 3 orders of magnitude. So something is missing in the<br />
technical analysis just comparing disk data rates which on average cannot go faster than 70 MB/s. Any clues??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-45278</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sat, 14 Jul 2007 16:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-45278</guid>
		<description>Up until the second half of last year, I used to complain that Netezza would talk to me about its customers but not its technology, and DATAllegro would talk about its technology but not its customers.

They still both have those orientations, but neither is nearly as extreme any more as they were.

CAM</description>
		<content:encoded><![CDATA[<p>Up until the second half of last year, I used to complain that Netezza would talk to me about its customers but not its technology, and DATAllegro would talk about its technology but not its customers.</p>
<p>They still both have those orientations, but neither is nearly as extreme any more as they were.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intrigued</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-45277</link>
		<dc:creator>Intrigued</dc:creator>
		<pubDate>Sat, 14 Jul 2007 16:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-45277</guid>
		<description>I've seen many articles like this where Stuart tries to position Datallegro over Netezza, the problem is Datallegro has hardly any customers on board, at least hardly any willing to talk about their success publicly, compare that to the momentum Netezza has in the marketplace, that speaks volumes to me !</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen many articles like this where Stuart tries to position Datallegro over Netezza, the problem is Datallegro has hardly any customers on board, at least hardly any willing to talk about their success publicly, compare that to the momentum Netezza has in the marketplace, that speaks volumes to me !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Data warehouse appliance hardware strategies</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-16582</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Data warehouse appliance hardware strategies</dc:creator>
		<pubDate>Sat, 27 Jan 2007 07:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-16582</guid>
		<description>[...] Netezza is Type 0 all the way. The product, if not the company, is built around its FPGA. [...]</description>
		<content:encoded><![CDATA[<p>[...] Netezza is Type 0 all the way. The product, if not the company, is built around its FPGA. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Data integration appliance vendor Cast Iron Systems</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-15063</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Data integration appliance vendor Cast Iron Systems</dc:creator>
		<pubDate>Fri, 05 Jan 2007 00:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-15063</guid>
		<description>[...] As for the hardware/platform side, it’s similar to what I’m hearing from other appliance vendors (Netezza and their emphasis on an FPGA are a real outlier). Namely: [...]</description>
		<content:encoded><![CDATA[<p>[...] As for the hardware/platform side, it’s similar to what I’m hearing from other appliance vendors (Netezza and their emphasis on an FPGA are a real outlier). Namely: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Philip Howard on Netezza</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-9521</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Philip Howard on Netezza</dc:creator>
		<pubDate>Wed, 04 Oct 2006 06:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-9521</guid>
		<description>[...] Philip Howard has published a write-up based on Netezza&#8217;s user conference, entertainly mixing fantasy and reality in his usual manner. Notably, he confuses Netezza&#8217;s zone maps, which are basically a very limited form of range partitioning, with something that can substitute for real indices. And the mind boggles at his implication that Netezza has neglected the FPGA in its overall market messaging. More understandable is his regurgitation of Netezza&#8217;s claims about heat and power, but although I must confess to not having checked either side&#8217;s arithmetic, I find Stuart Frost&#8217;s rebuttal in the comments to this thread pretty interesting. [...]</description>
		<content:encoded><![CDATA[<p>[...] Philip Howard has published a write-up based on Netezza&#8217;s user conference, entertainly mixing fantasy and reality in his usual manner. Notably, he confuses Netezza&#8217;s zone maps, which are basically a very limited form of range partitioning, with something that can substitute for real indices. And the mind boggles at his implication that Netezza has neglected the FPGA in its overall market messaging. More understandable is his regurgitation of Netezza&#8217;s claims about heat and power, but although I must confess to not having checked either side&#8217;s arithmetic, I find Stuart Frost&#8217;s rebuttal in the comments to this thread pretty interesting. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Frost</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-9377</link>
		<dc:creator>Stuart Frost</dc:creator>
		<pubDate>Tue, 03 Oct 2006 14:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-9377</guid>
		<description>Curt,

Just read another article that put Netezza's power consumption at around 30W per SPU. Since each SPU has one disk, that equates to 30W per disk.

Our nodes use around 420W each and have 12 disks, so that's 35W per disk. Our P Series gets slightly more usable space per disk than Netezza, so the consumption per TB is about the same.

If we compare to our C series, we get around four times the capacity per disk, so power consumption per TB is much lower.

Stuart
DATAllegro</description>
		<content:encoded><![CDATA[<p>Curt,</p>
<p>Just read another article that put Netezza&#8217;s power consumption at around 30W per SPU. Since each SPU has one disk, that equates to 30W per disk.</p>
<p>Our nodes use around 420W each and have 12 disks, so that&#8217;s 35W per disk. Our P Series gets slightly more usable space per disk than Netezza, so the consumption per TB is about the same.</p>
<p>If we compare to our C series, we get around four times the capacity per disk, so power consumption per TB is much lower.</p>
<p>Stuart<br />
DATAllegro</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Frost</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-6766</link>
		<dc:creator>Stuart Frost</dc:creator>
		<pubDate>Thu, 21 Sep 2006 03:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-6766</guid>
		<description>Curt,

According to your post, Netezza claims two major advantages from their use of FPGAs: 5X performance and lower heat and power consumption. Both are very easy to refute.

On performance, our latest version pretty much maxes out the disks at around 70MBps each. This is when running queries, not just simple table scans. Based on recent proof of concept projects, we've seen that Netezza does roughly the same. However, our performance is achieved through the use of smart software on commodity CPUs, rather than their combo of a CPU and an FPGA.

IMHO, our performance is even more impressive when you consider that we have just two dual-core CPUs for every twelve disks. In contrast, Netezza uses one CPU and one FPGA for every disk. Hence, our CPU:disk ratio is 1:3 compared with Netezza's 2:1.

This goes a long way in explaining our price advantage - our CPU cost per disk is much lower and this feeds directly into a significant advantage on both price/performance and price/capacity.

It also leads to a refutation of their supposed heat/power advantage. A single FPGA certainly does use less power than a dual core Xeon CPU. However, a typical Netezza installation uses far more chips for a given performance and capacity level.

To be specific, a Netezza 8650z has 33TB capacity and uses 672 SPUs with one Power CPU, an FPGA and one disk each. That's a total of 1,344 'CPUs' and 672 disks. In contrast, a DATAllegro P33 has 33TB capacity and uses 66 nodes with 2 dual core CPUs and 12 disks each for a total of 132 dual core CPUs and 792 disks.

With a similar number of disks being scanned at a similar rate, the two systems will have similar performance (until we take into account our sophisticated multi-level partitioning, which gives us a huge performance advantage on most queries). However, our system has less than one tenth the number of CPUs. I don't know how much power Netezza's FPGAs use, but I doubt it's less than a tenth of that used by one Xeon.

Our P33 is also less than half the price.

Stuart</description>
		<content:encoded><![CDATA[<p>Curt,</p>
<p>According to your post, Netezza claims two major advantages from their use of FPGAs: 5X performance and lower heat and power consumption. Both are very easy to refute.</p>
<p>On performance, our latest version pretty much maxes out the disks at around 70MBps each. This is when running queries, not just simple table scans. Based on recent proof of concept projects, we&#8217;ve seen that Netezza does roughly the same. However, our performance is achieved through the use of smart software on commodity CPUs, rather than their combo of a CPU and an FPGA.</p>
<p>IMHO, our performance is even more impressive when you consider that we have just two dual-core CPUs for every twelve disks. In contrast, Netezza uses one CPU and one FPGA for every disk. Hence, our CPU:disk ratio is 1:3 compared with Netezza&#8217;s 2:1.</p>
<p>This goes a long way in explaining our price advantage - our CPU cost per disk is much lower and this feeds directly into a significant advantage on both price/performance and price/capacity.</p>
<p>It also leads to a refutation of their supposed heat/power advantage. A single FPGA certainly does use less power than a dual core Xeon CPU. However, a typical Netezza installation uses far more chips for a given performance and capacity level.</p>
<p>To be specific, a Netezza 8650z has 33TB capacity and uses 672 SPUs with one Power CPU, an FPGA and one disk each. That&#8217;s a total of 1,344 &#8216;CPUs&#8217; and 672 disks. In contrast, a DATAllegro P33 has 33TB capacity and uses 66 nodes with 2 dual core CPUs and 12 disks each for a total of 132 dual core CPUs and 792 disks.</p>
<p>With a similar number of disks being scanned at a similar rate, the two systems will have similar performance (until we take into account our sophisticated multi-level partitioning, which gives us a huge performance advantage on most queries). However, our system has less than one tenth the number of CPUs. I don&#8217;t know how much power Netezza&#8217;s FPGAs use, but I doubt it&#8217;s less than a tenth of that used by one Xeon.</p>
<p>Our P33 is also less than half the price.</p>
<p>Stuart</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; No locks, no logs &#8212; no problem?</title>
		<link>http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-6587</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; No locks, no logs &#8212; no problem?</dc:creator>
		<pubDate>Wed, 20 Sep 2006 08:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/09/20/netezza%e2%80%99s-chip-story/#comment-6587</guid>
		<description>[...] There&#8217;s another cool-sounding part to the Netezza story, which straddles their chips and their software: The FPGA takes over the work of assuring database consistency. If the system attempts to read and write a record at the same time, the FPGA keeps thing straight. This eliminates the need for locks &#8212; at least if you don&#8217;t care about transactional integrity &#8212; and some of the reason for logs. (I guess that in lieu of any kind of rollback/rollforward they just rely on failover to mirrored disks.) [...]</description>
		<content:encoded><![CDATA[<p>[...] There&#8217;s another cool-sounding part to the Netezza story, which straddles their chips and their software: The FPGA takes over the work of assuring database consistency. If the system attempts to read and write a record at the same time, the FPGA keeps thing straight. This eliminates the need for locks &#8212; at least if you don&#8217;t care about transactional integrity &#8212; and some of the reason for logs. (I guess that in lieu of any kind of rollback/rollforward they just rely on failover to mirrored disks.) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
