<?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: Intel Nehalem Specification Comparison with AMD Core Architecture</title>
	<atom:link href="http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/</link>
	<description>Living Digitally and Electronically</description>
	<pubDate>Fri, 09 Jan 2009 09:26:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ulises Gomez</title>
		<link>http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/comment-page-1/#comment-532565</link>
		<dc:creator>Ulises Gomez</dc:creator>
		<pubDate>Fri, 26 Sep 2008 05:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/#comment-532565</guid>
		<description>Well, it seems like intel wants to push customers for wait its product until issues in Nehalem could be corrected, beacuse there are several faults on Nehalem architecture which are still not corrected. And here some reasons for What Intel wants to push customers for wait Nehalem (delayed compared to Shangai):

Intel's 6.4Gtransfer technology (Quickpath), can only transport 25BG/sec, against 6.4Gtransfer form Hyper Transport 3.1 which gives 52GB/sec (More than PCIe 2.0).

Beacuse of the deficit in Quickpath technology, Intel needs to bost up it's performance enabling HyperThreading per core, and using larger cache sizes, which really gives advantage in processing capabilities over Shangai (inside the processor) but, what about when it needs to be tranfered again to RAM and across the network?, only a word to describe this: bottleneck.</description>
		<content:encoded><![CDATA[<p>Well, it seems like intel wants to push customers for wait its product until issues in Nehalem could be corrected, beacuse there are several faults on Nehalem architecture which are still not corrected. And here some reasons for What Intel wants to push customers for wait Nehalem (delayed compared to Shangai):</p>
<p>Intel&#8217;s 6.4Gtransfer technology (Quickpath), can only transport 25BG/sec, against 6.4Gtransfer form Hyper Transport 3.1 which gives 52GB/sec (More than PCIe 2.0).</p>
<p>Beacuse of the deficit in Quickpath technology, Intel needs to bost up it&#8217;s performance enabling HyperThreading per core, and using larger cache sizes, which really gives advantage in processing capabilities over Shangai (inside the processor) but, what about when it needs to be tranfered again to RAM and across the network?, only a word to describe this: bottleneck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cssadc</title>
		<link>http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/comment-page-1/#comment-400439</link>
		<dc:creator>cssadc</dc:creator>
		<pubDate>Wed, 31 Oct 2007 17:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/10/31/intel-nehalem-specification-comparison-with-amd-core-architecture/#comment-400439</guid>
		<description>what a great "NEWS"!

hell when you have no info then write nothing.
whats up with you guys?  this info is out for ages.. nothing new..... and where is the comparisation... you suck....</description>
		<content:encoded><![CDATA[<p>what a great &#8220;NEWS&#8221;!</p>
<p>hell when you have no info then write nothing.<br />
whats up with you guys?  this info is out for ages.. nothing new&#8230;.. and where is the comparisation&#8230; you suck&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
