Intel Core Duo (Yonah) Performance Preview - Part II
by Anand Lal Shimpi on December 19, 2005 12:55 PM EST- Posted in
- CPUs
What about Clock Speeds?
Whereas the Pentium 4's extremely deep pipeline made clock-for-clock comparisons to the Athlon 64 virtually meaningless, the Pentium M and Yonah processors feature far shorter pipelines akin to AMD's architecture.
The Athlon 64 features a 12-stage integer pipeline, and while Intel has never specifically disclosed the length of Yonah's pipeline, they have made two important statements: it is longer than the Pentium III's 10-stage integer pipeline, and shorter than Conroe/Merom's 14-stage pipeline. Given the relatively tight range, Yonah's pipeline can pretty much be considered to be very similar to AMD's Athlon 64, give or take a stage of the pipeline.
The net result is that we can draw some valid conclusions based on comparisons of Yonah to the Athlon 64 X2 at similar clock speeds.
But our Yonah sample ran at 2.0GHz, which ends up being the speed of the slowest Athlon 64 X2 that is currently available: the 3800+. The highest end Athlon 64 X2s currently run at 2.4GHz, with high speeds just around the corner. So the question isn't just how competitive Yonah is at 2.0GHz, but rather, how high can Yonah go? Unfortunately, our test platform wouldn't allow us to overclock our chip very far, but thankfully, we have access to a decent amount of Intel's future roadmaps, so we can at least see what's going to happen to Yonah over the next year.
While Yonah will make its debut at a maximum speed of 2.16GHz, it will actually only receive a single speed bump before Merom's release at the end of the year. That means that we'll see a 2.33GHz Yonah after the middle of the year, but we'll have to turn to Merom to get any higher clock speeds.
Looking back to our initial articles on the Pentium M's architecture, you'll remember that one of the important aspects of its design is that all critical paths in the chip were slowed down to meet a maximum clock target. This means that Intel set a clock target for the CPU and made sure that the chip ran at that speed or below, and did not optimize any paths that would have allowed the CPU to run higher. Instead, the Pentium M team depended on the manufacturing folks to give them additional clock speed headroom by providing smaller manufacturing processes every 2 years. In other words, the Pentium M was never designed for high clock speeds, which is why it debuted at 1.5GHz and still has not even reached 2.33GHz today.
Intel's next-generation microarchitecture hopes to change that approach ever so slightly by introducing a longer pipeline into the equation, but on a much more conservative basis than the Pentium 4 did just 5 years ago. Conroe (desktop), Merom (mobile) and Woodcrest (server) will feature a 14-stage integer pipeline, which will allow for higher clock speeds than what Yonah could pull through. We would expect a debut at a minimum of 2.4GHz and probably at least one speed grade higher. Learning from their mistakes with the Pentium 4, Intel will balance the reduction in efficiency of a deeper pipeline with a wider 4-issue core (vs. the current 3-issue core used in Yonah).
So it looks like Intel's plan for 65nm is to rely on their deeper pipelined processors (Conroe/Merom/Woodcrest) for higher clock speed, with Yonah falling below the 2.5GHz mark. And based on what we've seen in the first article, a 2.33GHz Yonah would be competitive with an Athlon 64 X2 4600+, but definitely not outpacing it. This does bode well for Intel's next-generation processors, especially on the desktop with Conroe.
If the move to a 4-issue core is able to balance out the negative impact of a deeper pipeline (which admittedly it may or may not do in all cases), a higher clock speed desktop part should be very good competition for AMD's offerings. Although based on what we've seen thus far, we would be surprised if Conroe vs. Athlon 64 was a blow-out in favor of either manufacturer; more and more, it is looking like Conroe will simply bring Intel up to par with AMD, ahead in some areas, behind in others, and with the lower power advantage as long as AMD is still at 90nm.
Why the X2 and why not Turion?
One of the other questions that we were asked a lot after the first article was why we insisted on comparing a mobile Yonah processor to a desktop Athlon 64 X2, and not an AMD Turion 64. Our reasoning was obvious to some, but we felt it made sense to present it more clearly here:
Whereas the Pentium 4's extremely deep pipeline made clock-for-clock comparisons to the Athlon 64 virtually meaningless, the Pentium M and Yonah processors feature far shorter pipelines akin to AMD's architecture.
The Athlon 64 features a 12-stage integer pipeline, and while Intel has never specifically disclosed the length of Yonah's pipeline, they have made two important statements: it is longer than the Pentium III's 10-stage integer pipeline, and shorter than Conroe/Merom's 14-stage pipeline. Given the relatively tight range, Yonah's pipeline can pretty much be considered to be very similar to AMD's Athlon 64, give or take a stage of the pipeline.
The net result is that we can draw some valid conclusions based on comparisons of Yonah to the Athlon 64 X2 at similar clock speeds.
But our Yonah sample ran at 2.0GHz, which ends up being the speed of the slowest Athlon 64 X2 that is currently available: the 3800+. The highest end Athlon 64 X2s currently run at 2.4GHz, with high speeds just around the corner. So the question isn't just how competitive Yonah is at 2.0GHz, but rather, how high can Yonah go? Unfortunately, our test platform wouldn't allow us to overclock our chip very far, but thankfully, we have access to a decent amount of Intel's future roadmaps, so we can at least see what's going to happen to Yonah over the next year.
While Yonah will make its debut at a maximum speed of 2.16GHz, it will actually only receive a single speed bump before Merom's release at the end of the year. That means that we'll see a 2.33GHz Yonah after the middle of the year, but we'll have to turn to Merom to get any higher clock speeds.
Looking back to our initial articles on the Pentium M's architecture, you'll remember that one of the important aspects of its design is that all critical paths in the chip were slowed down to meet a maximum clock target. This means that Intel set a clock target for the CPU and made sure that the chip ran at that speed or below, and did not optimize any paths that would have allowed the CPU to run higher. Instead, the Pentium M team depended on the manufacturing folks to give them additional clock speed headroom by providing smaller manufacturing processes every 2 years. In other words, the Pentium M was never designed for high clock speeds, which is why it debuted at 1.5GHz and still has not even reached 2.33GHz today.
Intel's next-generation microarchitecture hopes to change that approach ever so slightly by introducing a longer pipeline into the equation, but on a much more conservative basis than the Pentium 4 did just 5 years ago. Conroe (desktop), Merom (mobile) and Woodcrest (server) will feature a 14-stage integer pipeline, which will allow for higher clock speeds than what Yonah could pull through. We would expect a debut at a minimum of 2.4GHz and probably at least one speed grade higher. Learning from their mistakes with the Pentium 4, Intel will balance the reduction in efficiency of a deeper pipeline with a wider 4-issue core (vs. the current 3-issue core used in Yonah).
So it looks like Intel's plan for 65nm is to rely on their deeper pipelined processors (Conroe/Merom/Woodcrest) for higher clock speed, with Yonah falling below the 2.5GHz mark. And based on what we've seen in the first article, a 2.33GHz Yonah would be competitive with an Athlon 64 X2 4600+, but definitely not outpacing it. This does bode well for Intel's next-generation processors, especially on the desktop with Conroe.
If the move to a 4-issue core is able to balance out the negative impact of a deeper pipeline (which admittedly it may or may not do in all cases), a higher clock speed desktop part should be very good competition for AMD's offerings. Although based on what we've seen thus far, we would be surprised if Conroe vs. Athlon 64 was a blow-out in favor of either manufacturer; more and more, it is looking like Conroe will simply bring Intel up to par with AMD, ahead in some areas, behind in others, and with the lower power advantage as long as AMD is still at 90nm.
Why the X2 and why not Turion?
One of the other questions that we were asked a lot after the first article was why we insisted on comparing a mobile Yonah processor to a desktop Athlon 64 X2, and not an AMD Turion 64. Our reasoning was obvious to some, but we felt it made sense to present it more clearly here:
- As much as Yonah is a mobile processor, it is a great indicator of the performance of Intel's future desktop processors based on the Conroe core. AMD has already stated that beyond moving to Socket-M2 and some minor updates, there will be no significant architectural changes to the Athlon 64 line next year. In other words, we know for the most part how AMD's going to be performing next year, but we have no clue how Intel will towards the end of 2006; Yonah helps us fill in the blanks.
- AMD will have a dual core Turion based mobile processor out sometime in 2006. However, it will be based on AMD's Socket-M2 platform, meaning that it will include DDR2 support. Given that we don't know exactly how DDR2 is going to impact the Athlon 64's performance, we couldn't accurately simulate the performance of AMD's upcoming dual core Turion. Comparing a dual-core Yonah to AMD's single-core Turion also wouldn't be too valid a comparison either.
Facebook
Twitter
RSS
103 Comments
View All Comments
mitcoes - Saturday, April 22, 2006 - link
The msot important question about corel duo, is if dual processors Apple Machines with ATI X1900XT woul be a better machine than AMD and Pentium with one processor at same clocks. Better when core duo would arrive to 3 Mhz or nearby. Becouse hard gamers, and renderers would buy this (expending a few more bucks) and have the choice of use MAC OS, Win XP, an Linux on the same machine with opengl games probably going better in Leopard than in XP becouse of the better networking of UNIX and Linux over TCP/IP. The test of packets losed with Quake3 XP vs Leopard would be a great test, becouse probably AMD, and Pentium with same clocks and ATI would have similar preformance in games that are not prepared for two processors, but Photoshop CS2, blender And other CAD/CAM apps would run better. Perhaps The future new market of Apple machines are hard gamers, and hard users like architects, renderers, animators and so one. But it must be tested. And I want to know if MAC mainboards are better than ASUS and Gigabyte ones (or other better if them exists).Cygni - Wednesday, December 21, 2005 - link
Congrat AT commenters! I have to say, this is the new HIGH SCORE for useless, incorrect, biased, self important posts in the history of AT!Really, i was going to respond to each one in turn, but I think its far easier just to make this one post where i point out that many, many, many of you should likely try lurking a bit instead of instantly hitting the reply button and spouting off about latencys, bus widths, and other thing your Toms Hardware Education degree has certified you an expert at. We will all be more intelligent if you didnt post.
IntelUser2000 - Tuesday, December 20, 2005 - link
They should have used low latency DDR2-533 rather than the normal JEDEC specified 4-4-4-12 latency for their reviews. It might be faster then :)).Also, testing Sonoma notebooks have shown that it likes single channel DDR2-533 better than DDR2-400, like how it doesn't benefit from dual channel. I would also like to see DDR2-667 results(over dual channel DDR2-533), as few % here and there will really show Yonah's potential.
coldpower27 - Tuesday, December 20, 2005 - link
Yes that would be interesting, as Anantech does have Corsair DDR2-667 3-2-2-8 available in their repitoire.StuckMojo - Tuesday, December 20, 2005 - link
I'd like to see compilation benchmarks. Lots of us use our laptops for software development.
Betwon - Tuesday, December 20, 2005 - link
Compilation?At the recent Spec CPU Cint2000 test--The most fast x86 CPU about compiler is P4 670.
176.gcc 2195/2195 ponits
PM@2.26GHz(1995/1994) is fast than FX-55@2.6GHz(1931/1933).
IntelUser2000 - Tuesday, December 20, 2005 - link
If any of you actually care to search for transistor performance of Intel's and AMD/IBM, you can see that AMD/IBM's the newest 65nm process is only 2-3% faster but Intel is providing the numbers at HALF the leakage.There WILL be X2 clock speed like versions of Yonah with higher TDP and being graded as EE.
-Equal platform comparisons are never possible.
-DDR2's power advantage isn't as great as you think.
-We don't know if Turion would benefit at all from DDR2 in performance, the claimed 15% or so is at best case, aka single benchmark. It always happens, companies say some wonder number and in reality its even worse than the previous one.
Betwon - Tuesday, December 20, 2005 - link
The very low latency of L2 cache is the main real reason? AT may be foreget that L2 can be shared, which is different with AMD.Schmide - Tuesday, December 20, 2005 - link
Correct me if I'm wrong. Doesn't the AMD architecture have a 3 cycle L1 latency due to an exclusive L1 L2 cache relationship. While Intel uses a 2 cycle L1 inclusive L1 L2 cache relationship. With the larger cache sizes now, the more costly exclusive set seems to be holding AMD back. However, this higher latency could be the reason AMD is able to reach higher speeds using a lower process.As for the power consumption, I wonder if the board design had anything to do with the X2 being 30% higher. Chime in here
On die memory controller advantage AMD.
DDR2 lower power consumption advantage Intel
65nm process advantage Intel
Mature SOI advantage AMD.
Betwon - Tuesday, December 20, 2005 - link
You are wrong about the cache of Yonah. The mobile CPU is different with the Netburst.Yonah's L1 latency is 3 cycles, and it is a kind of write-back cache, which needs not always copy the data to L2. L2 latency is 14 cycles(AT said), which is the same with AthonX2. And Yonah's number of pipeline stages is 11,12, or 13. The AthonX2 is 12-stage. So, (Include AT)we believe that Yonah can reach the high frequency. The real reason of Yonah only max 2.16GHz -- for the moblie applications ... to control the power sum.