<?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: Towards an Industry Standard for Benchmarking Big Data Workloads</title>
	<atom:link href="http://blogs.cisco.com/datacenter/towards-an-industry-standard-for-benchmarking-big-data-workloads/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com/datacenter/towards-an-industry-standard-for-benchmarking-big-data-workloads/</link>
	<description></description>
	<lastBuildDate>Thu, 20 Jun 2013 00:19:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Ken North</title>
		<link>http://blogs.cisco.com/datacenter/towards-an-industry-standard-for-benchmarking-big-data-workloads/#comment-605997</link>
		<dc:creator>Ken North</dc:creator>
		<pubDate>Sat, 23 Jun 2012 13:48:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.cisco.com/?p=67639#comment-605997</guid>
		<description><![CDATA[Dr. Dobb&#039;s is running the first of two blog posts about benchmarks, the TPC, the TPCTC 2012 conference and the new TPC-DS benchmark.

&quot;100 GB to 30,000 GB: Size, Speed and Benchmarks&quot;
http://bit.ly/MEDp3J]]></description>
		<content:encoded><![CDATA[<p>Dr. Dobb&#8217;s is running the first of two blog posts about benchmarks, the TPC, the TPCTC 2012 conference and the new TPC-DS benchmark.</p>
<p>&#8220;100 GB to 30,000 GB: Size, Speed and Benchmarks&#8221;<br />
<a href="http://bit.ly/MEDp3J" rel="nofollow">http://bit.ly/MEDp3J</a>
<p class="comment-like"><img class="comment-like-btn" title="Vote" onclick="cl_like_this('http://blogs.cisco.com/wp-admin/admin-ajax.php',605997)" src="http://blogs.cisco.com/wp-content/plugins/comments-likes/images/like.png" />&nbsp;&nbsp;&nbsp;<span id="comment-like-cnt-605997">0</span> likes</p>
]]></content:encoded>
	</item>
</channel>
</rss>
