Intel's Core 2 Extreme & Core 2 Duo: The Empire Strikes Back
by Anand Lal Shimpi on July 14, 2006 12:00 AM EST- Posted in
- CPUs
New Pricing
As you will soon see, Intel's new Core 2 lineup has basically made all previous Intel processors worthless. The performance of the new Core 2 CPUs is so much greater, with much lower power consumption, that owners of NetBurst based processors may want to dust off the old drill bits and make some neat looking keychains.
Intel also realizes that its new Core 2 line will make its older Pentium D and Pentium Extreme Edition processors seem a bit homely, and thus it will significantly reduce the pricing on some of the CPUs by the end of this month to help spruce them up a bit.
Intel's new pricing, effective starting July 23rd, is listed below:
| CPU | Clock Speed | L2 Cache | Price |
| Intel Core 2 Extreme X6800 | 2.93GHz | 4MB | $999 |
| Intel Core 2 Duo E6700 | 2.66GHz | 4MB | $530 |
| Intel Core 2 Duo E6600 | 2.40GHz | 4MB | $316 |
| Intel Core 2 Duo E6400 | 2.13GHz | 2MB | $224 |
| Intel Core 2 Duo E6300 | 1.86GHz | 2MB | $183 |
| Intel Pentium D 945 | 3.40GHz | 2MBx2 | $163 |
| Intel Pentium D 915 | 2.80GHz | 2MBx2 | $133 |
| Intel Pentium D 820 | 2.80GHz | 1MBx2 | $113 |
| Intel Pentium D 805 | 2.66GHz | 1MBx2 | $93 |
The table above only showcases the NetBurst CPUs that are actually cheaper than their Core 2 counterparts; there are a number that are priced equal to Core 2 options, but you'll want to stay away from those (more blatant foreshadowing).
Unfortunately AMD won't have an architectural update of the Athlon 64 X2 until sometime in 2007 or 2008, thus its only response to Intel's Core 2 lineup today is to also reduce pricing. Shortly before today's launch AMD informed us that more aggressive price cuts for the Athlon 64 X2 line were coming in July, but we couldn't get any more specific information. The best numbers we've got are those that were leaked shortly after Computex, which may end up being higher than what AMD is now thinking of doing:
| CPU | Clock Speed | L2 Cache | Projected Price |
| AMD Athlon 64 X2 5000+ | 2.6GHz | 512KBx2 | $403 |
| AMD Athlon 64 X2 4600+ | 2.4GHz | 512KBx2 | $301 |
| AMD Athlon 64 X2 4200+ | 2.2GHz | 512KBx2 | $240 |
| AMD Athlon 64 X2 3800+ | 2.0GHz | 512KBx2 | $169 |
In order to keep prices competitive, AMD is also killing off its Athlon 64 X2s with a 1MB L2 cache. By only shipping 512KB parts (except for the limited quantities of FX processors that are sold), AMD can produce more CPUs per wafer and thus help increase supply and offer lower prices.
Below we've compared both AMD and Intel's proposed price cuts, and as you can see, AMD needs to do a lot more in order to remain competitive.
| CPU | Clock Speed | L2 Cache | Price |
| Intel Core 2 Extreme X6800 | 2.93GHz | 4MB | $999 |
| Intel Core 2 Duo E6700 | 2.66GHz | 4MB | $530 |
| AMD Athlon 64 X2 5000+ | 2.6GHz | 512KBx2 | $403* |
| Intel Core 2 Duo E6600 | 2.40GHz | 4MB | $316 |
| AMD Athlon 64 X2 4600+ | 2.4GHz | 512KBx2 | $301* |
| AMD Athlon 64 X2 4200+ | 2.2GHz | 512KBx2 | $240* |
| Intel Core 2 Duo E6400 | 2.13GHz | 2MB | $224 |
| Intel Core 2 Duo E6300 | 1.86GHz | 2MB | $183 |
| AMD Athlon 64 X2 3800+ | 2.0GHz | 512KBx2 | $169* |
| Intel Pentium D 945 | 3.40GHz | 2MBx2 | $163 |
| Intel Pentium D 915 | 2.80GHz | 2MBx2 | $133 |
| Intel Pentium D 820 | 2.80GHz | 1MBx2 | $113 |
| Intel Pentium D 805 | 2.66GHz | 1MBx2 | $93 |
*Note: The AMD prices are still rumored. We're waiting for final confirmation from AMD for accuracy.
Based on these prices, AMD's Athlon 64 X2 4600+ would have to beat Intel's E6600, the 4200+ would have to beat the E6400 and the X2 3800+ would have to be somewhere in between the performance of a Pentium D 940/945 and an E6300.
We're getting the impression that AMD may be cutting prices more than what we've seen here, but we have no idea to what degree yet. By the end of this year AMD will also offer higher clock speeds as well as its new 4x4 platform (dual socket, dual core desktop Athlon 64 FX motherboards), but that's all we can expect for the foreseeable future.
Facebook
Twitter
RSS
202 Comments
View All Comments
crystal clear - Saturday, July 15, 2006 - link
Just to remind all that-" Intel decides to release a B2 stepping of its Conroeprocessors.Also
BEWARE of Engineering samples & reviews based on Engineering samples inlcuded.
OcHungry - Saturday, July 15, 2006 - link
I don’t know if this Q been asked or answered (sorry no time reading 120 posts)Bu Mr. Anand, can I kindly ask you couple of concerns:
1) why don’t we see any reference to temp. under load? Temp. is a crucial factor in deciding wether or not I buy conroe since I live in a very hot climate.
2)A lot people make reference to 64bit and window vista and that conroe is a 32bit architecture and will not perform as good in 64bit. Is it true? can we have some 64bit benchmarks? It would be great to do this test in multitasking.
3) I have also noticed (from so many who have had pre-release ES @ XS, and other forums) that overclocked conroe does not correspond directly to performance, unlike A64.
What I mean is: If A64 is overclocked 20%, the performance increases ~20% 9more or less, in most cases), But have not seen this to hold w/ conroe. So I am wondering what would happen if we put a low end conroe, such as E6400 against A64 4000 x2, 2x1mb cache (same price range after price drop) and overclock them to their limit, using stock cooling, and do the benchmarks (64bit included). The reason I am interested in this type of review is because I am an average end user on budget and would like to know which would give me better price/performance. I think I am speaking for at least 90% of consumers. Not everyone buys $1000 cpu and consumers on budget is detrimental to survival of conroe or AM2 cpus. This alone should give you enough incentive to put together a review oriented around us, the mainstream computer users. We can make or break any chipmaker.
So please Mr. Anad, can we have another review along those lines described above?
We greatly appreciate it.
Thanks,
ochungry
aznskickass - Saturday, July 15, 2006 - link
Hey ochungry, I believe Xbitlabs did an overclocking comparison between a Conroe E6300 and an A64 X2 3800+, and while they didn't do any 64bit benchmarks, the conclusion is that at stock speeds the E6300 is slightly faster than X2 3800+, and when both are overclocked to the max, E6300's lead increases even more.Here is the review/comparison:
http://xbitlabs.com/articles/cpu/display/core2duo-...">http://xbitlabs.com/articles/cpu/display/core2duo-...
OcHungry - Saturday, July 15, 2006 - link
Those guys @ X-bit lab do not fool me. And I hope Anandtech conducts the same test w/ best suited memory module for “BOTH” platforms. We know (so as Xbitlab knows) that, because of IMC, A64 performs its best @ tightest memory timings. X-bit lab should have used http://www.newegg.com/Product/Product.asp?Item=N82...">This memory module if the test was going to be fair and square. Furthermore A64 3800 x2 @ 3ghz is 10x300, which means DDR2 667 1:1 could have been better to use. This http://www.newegg.com/Product/Product.asp?Item=N82...">DDR2 667 @ 3-3-3-10 would have given about 10% better performance than DDR2 4-4-4-12 that they used. X-bit does not mention anything about memory/cpu ratio. What divider was used? Was it 133/266? Or as close to 1:1 as possible? Sooner or later the truth will prevail when we end users try it for ourselves (oh BTW, not ES), and we will see if xbitlab and others were genuinely interested on behalf of consumers, or the interest destined to ill-fated purpose. Will not accuse anyone, but it all look very fishy.I am certain that Mr. Anad will clear all these conspicuous reviews , and hand us another that concerns the consumer’s majority- us average users.
IntelUser2000 - Saturday, July 15, 2006 - link
W-R-O-N-G!!! DDR2-800 at EVEN slower 5-5-5-15 timings is FASTER THAN DDR2-667 3-3-3-10: http://xbitlabs.com/articles/cpu/display/amd-socke...">http://xbitlabs.com/articles/cpu/display/amd-socke...
Prefer AT's results?: http://www.anandtech.com/cpuchipsets/showdoc.aspx?...">http://www.anandtech.com/cpuchipsets/showdoc.aspx?...
DDR2-800 is faster. The myth that it performs amazingly better(comparatively) with lower latency is just, a myth. I believe there was a thread in forums that tells exactly that.
OcHungry - Sunday, July 16, 2006 - link
Iguess you don’t understand much about AMD's memory latency, direct connect, and 1:1 ratio.It is not like Intel's illusionary, that faster than FSB is better. It is not and is useless. Anad proved it here. But this subject has a tendency to be dragged on for ever by those who don’t understand the concept of IMC. So it's better leave it alone.
But I still would like to see tightest timing and 1:1 ratio. It is now clear to me that those reviews in favor of Intel, artfully evade this argument/request, knowing it will give AMD advantage over Intel's FSB.
aznskickass - Sunday, July 16, 2006 - link
*sigh*How is the AMD disadvantaged if BOTH platforms are reviewed using the same RAM?
AMD needs ultra low latency DDR2 to attain best performance? Well, bad luck, Intel doesn't , there is no 'deliberate' conspiracy to put AMD in a bad light.
Look, if you just want to hang on to the notion that AMD has been cheated in the reviews, then go ahead and get your X2 4200+ and see how close you can get to Conroes numbers.
I'll be using my E6600 @ 3.5GHz+ and laughing at your stupidity.
aznskickass - Saturday, July 15, 2006 - link
I consider Xbitlabs to be one of the more trustworthy sites around, and do note that they are testing mainstream chips, and expensive CL3 DDR2 just doesn't make sense in a budget setup, which further puts Conroe in a good light, as it doesn't require expensive CL3 DDR2 to perform well.sum1 - Friday, July 14, 2006 - link
A good read. For the editor, I found 4 errors, search the full lines of text below at:http://www.anandtech.com/printarticle.html?i=2795">http://www.anandtech.com/printarticle.html?i=2795
That begin said,
and H.264 in coding
as soon as its available
at the fastest desktop processor we've ever tested
("and" would be more readable that "at" in this sentence)
JarredWalton - Friday, July 14, 2006 - link
Thanks. At least one of those (in coding) can be blamed on my use of Dragon NaturallySpeaking and not catching the error. The others... well, they can be blamed on me not catching them too. LOL. The last one is sort of a difference of opinion, and I've replaced the comma with a dash, as that was the intended reading. :)--Jarred