<?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: The questionable benefits of terabyte-scale data warehouse virtualization</title>
	<atom:link href="http://www.dbms2.com/2009/02/23/the-questionable-benefits-of-terabyte-scale-data-warehouse-virtualization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2009/02/23/the-questionable-benefits-of-terabyte-scale-data-warehouse-virtualization/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Thu, 09 Feb 2012 21:52:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Steve Wooledge</title>
		<link>http://www.dbms2.com/2009/02/23/the-questionable-benefits-of-terabyte-scale-data-warehouse-virtualization/#comment-111370</link>
		<dc:creator>Steve Wooledge</dc:creator>
		<pubDate>Mon, 23 Feb 2009 20:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=700#comment-111370</guid>
		<description>We have seen virtualization work well (or is required) in a couple use-cases:

[1] Internal testing: Aster Data has used virtualization to test/QA our DBMS on &gt; 200 virtualized nodes. (note we have production customer with ~100 nodes)

[2] Cloud computing: ShareThis runs a 3+ TB Aster nCluster system on Amazon Web Services, which is virtualized on their Amazon machine images (AMI&#039;s). You can listen to ShareThis talk about their ability to scale up/down with no downtime because of the way we handle data movement/admin complete online: https://asterdata.webex.com/asterdata/lsr.php?AT=pb&amp;rID=29679512&amp;rKey=98F898EA5CCA0BE8 
note ShareThis also handles full and incremental backups online)</description>
		<content:encoded><![CDATA[<p>We have seen virtualization work well (or is required) in a couple use-cases:</p>
<p>[1] Internal testing: Aster Data has used virtualization to test/QA our DBMS on &gt; 200 virtualized nodes. (note we have production customer with ~100 nodes)</p>
<p>[2] Cloud computing: ShareThis runs a 3+ TB Aster nCluster system on Amazon Web Services, which is virtualized on their Amazon machine images (AMI&#8217;s). You can listen to ShareThis talk about their ability to scale up/down with no downtime because of the way we handle data movement/admin complete online: <a href="https://asterdata.webex.com/asterdata/lsr.php?AT=pb&amp;rID=29679512&amp;rKey=98F898EA5CCA0BE8" rel="nofollow">https://asterdata.webex.com/asterdata/lsr.php?AT=pb&amp;rID=29679512&amp;rKey=98F898EA5CCA0BE8</a><br />
note ShareThis also handles full and incremental backups online)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tzahi jakubovitz</title>
		<link>http://www.dbms2.com/2009/02/23/the-questionable-benefits-of-terabyte-scale-data-warehouse-virtualization/#comment-111369</link>
		<dc:creator>tzahi jakubovitz</dc:creator>
		<pubDate>Mon, 23 Feb 2009 20:43:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=700#comment-111369</guid>
		<description>What you say is definitely valid. I would like to present a different view.
The flexibility of virtual machines is very important. the fact you can develop on a virtual machine, and then just copy the virtual machine to the production server, duplicate it as many times as you need. Add machines without changing database configuration - this makes everything move faster.
In a few months - we will have 6 core CPUs. So paying about 10% CPU overhead is not critical.
I do not know if disks cannot be stressed by ESX. EMC claims that an ESX server is capable of 63,000 IOs per second.
It reminds me of the C++ vs Java issues. You pay in CPU cycles for modern language. But the flexibility makes it worthwhile, and sometimes enables you to work smarter and build a faster solution.
Sure - If you build the world&#039;s largest warehouse, VMware will probably not be a good choice. But most of us are building medium solutions, and flexibility is worth losing 10% CPU.</description>
		<content:encoded><![CDATA[<p>What you say is definitely valid. I would like to present a different view.<br />
The flexibility of virtual machines is very important. the fact you can develop on a virtual machine, and then just copy the virtual machine to the production server, duplicate it as many times as you need. Add machines without changing database configuration &#8211; this makes everything move faster.<br />
In a few months &#8211; we will have 6 core CPUs. So paying about 10% CPU overhead is not critical.<br />
I do not know if disks cannot be stressed by ESX. EMC claims that an ESX server is capable of 63,000 IOs per second.<br />
It reminds me of the C++ vs Java issues. You pay in CPU cycles for modern language. But the flexibility makes it worthwhile, and sometimes enables you to work smarter and build a faster solution.<br />
Sure &#8211; If you build the world&#8217;s largest warehouse, VMware will probably not be a good choice. But most of us are building medium solutions, and flexibility is worth losing 10% CPU.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

