Intel Penryn Performance Preview: The Fastest gets Faster
by Anand Lal Shimpi on April 18, 2007 8:00 AM EST- Posted in
- CPUs
Penryn Performance at 3.33GHz in Beijing
Next up are Intel's Penryn benchmark results revealed at IDF Beijing. The system configuration is a little different, as both Penryn systems run at 3.33GHz and the systems are running Windows Vista Ultimate 32-bit. The exact config is listed below:
Test System Configuration | Wolfdale 3.33GHz | Yorkfield 3.33GHz | Core 2 Extreme QX6800 (2.93GHz) |
CPU | Pre-production dual core Penryn 3.33GHz/1333MHz FSB 6MB L2 |
Pre-production quad core Penryn 3.33GHz/1333MHz 12MB L2 |
Core 2 Extreme QX6800 quad core 2.93GHz/1066MHz 8MB L2 |
Motherboard | Pre-production BadAxe2 975X |
Pre-production BadAxe2 975X |
BadAxe2 975X |
BIOS | Pre-production BIOS |
Pre-production BIOS |
Pre-production BIOS |
Chipset Driver |
|
8.1.1.1010 |
8.1.1.1010 |
Video Card | GeForce 8800 GTX |
||
Video Driver | NVIDIA 100.65 |
||
Memory | 2 x 1GB DDR2-800 5-5-5-15 |
||
Hard Drive | Seagate 7200.10 320GB |
And now the results:
Benchmark | Wolfdale 3.33GHz | Yorkfield 3.33GHz | Core 2 Extreme QX6800 (2.93GHz) |
3DMark '06 V1.1.0 Pro CPU (score) : | 3061 |
4957 |
4070 |
3DMark '06 V1.1.0 Pro Overall (score) : | 11015 |
11963 |
11123 |
Mainconcept H.264 Encoder (seconds) : | 119 |
73 |
89 |
Cinebench R9.5 (CPU test) | 1134 |
1935 |
1549 |
Cinebench R10 Beta (CPU test) | 7045 |
13068 |
10416 |
HL2 Lost Coast Build 2707 (fps) : | 210 |
210 |
153 |
DivX 6.6 Alpha w/ VirtualDub 1.7.1 (seconds) | 22 |
18 |
38 |
For easier comparison we took the two quad-core chips (Yorkfield vs. Kentsfield) and looked at performance scaling between the two:
Benchmark | Yorkfield Performance Advantage |
3DMark '06 V1.1.0 Pro CPU (score) : | 21.8% |
3DMark '06 V1.1.0 Pro Overall (score) : | 7.6% |
Mainconcept H.264 Encoder (seconds) : | 18.0% |
Cinebench R9.5 (CPU test) | 24.9% |
Cinebench R10 Beta (CPU test) | 25.5% |
HL2 Lost Coast Build 2707 (fps) : | 37.3% |
DivX 6.6 Alpha w/ VirtualDub 1.7.1 (seconds) | 111% |
The Yorkfield system runs at a 13.6% higher clock speed than the Kentsfield system giving it an inherent advantage, but that's clearly not all that's making it faster. Half-Life 2 went up an expected 21.8% (we're assuming that Intel ran these numbers at 1024 x 768), and Cinebench saw a 25% increase in performance.
The DivX 6.6 test is particularly strong for Intel because it is using an early alpha version of DivX with support for SSE4. With SSE4 support, the quad-core Yorkfield processor ends up being more than 50% faster than Kentsfield, which bodes very well for Penryn if applications like DivX can bring SSE4 support in time for launch.
Final Words
Obviously we'll reserve final judgments on Penryn for our official review of the CPU, but these initial results look very promising. We would expect to see clock for clock Penryn vs. Conroe improvements to be in the 5 - 10% range at minimum depending on the application. Factor in higher clock speeds and you can expect our CPU performance charts to shift up by about 20% by the end of this year.
Intel has shown its cards, now it's time for AMD to respond with those long overdue Barcelona tests...
66 Comments
View All Comments
OcHungry - Thursday, April 19, 2007 - link
AMD's 65nm K10 will beat Intel's 45nm Penryn by 20%, my prediction.TA152H - Thursday, April 19, 2007 - link
You picking the Cubs to win the World Series?Thatguy97 - Thursday, June 18, 2015 - link
lol funny after 8 yearsKougar - Thursday, April 19, 2007 - link
Is there any info whatsoever regarding QuadCore pricing for the desktop with Kentsfield's successor? It would be very helpful to know if there might be a version of Yorkfield matching the $266 Q6600 price tag come next January... :)theprodigalrebel - Wednesday, April 18, 2007 - link
The Yorkfield-Kentsfield comparison looks correct.In the CPU-only Test, Yorkfield scores 887 points more (4957 vs 4070)
In the Overall Test, Yorkfield scores 840 points more (11963 vs 11123)
But the Yorkfield-Wolfdare scores look off...
In the CPU-only Test, Yorkfield scores 1896 points more than Wolfdale. (4957 vs 3061)
In the Overall Test, Yorkfield only scores 948 points more than Wolfdale. (11964 vs 11015)
I'm guessing the Wolfdale Overall Score should read 10015?
Shintai - Thursday, April 19, 2007 - link
Because 3Dmark score aint calculated like that.Check this.
http://www.thg.ru/graphic/3dmark06/images/3dmarkca...">http://www.thg.ru/graphic/3dmark06/images/3dmarkca...
And to add alittle fun:
http://img374.imageshack.us/img374/5569/654545fd7....">http://img374.imageshack.us/img374/5569/654545fd7....
If you take a E6600 CPU, and pair it with an inifity super performing GPU. Your score couldnt be over 35000.
Same reason, just the other way. On why the score doesnt increase with the same value.
kilkennycat - Wednesday, April 18, 2007 - link
I agree totally with the last sentence of this article. A Barcelona series of Penryn-like demonstrations and tests is many months overdue. Has AMD got serious design problems, or does the "emperor really have no clothes" with respect to Barcelona's performance ?Any hope of AMD recovering development costs with premium prices on the Barcelona family will be quashed if Intel chooses to counter with early release of Penryn-family CPUs and simultaneously undercut the AMD prices. Time to consider selling AMD stock short again?
archcommus - Wednesday, April 18, 2007 - link
I fear that AMD has not released early benches because the performance is not what they're hoping for compared to what Intel is giving out. Intel is being boastful and giving out lots of info because they know what they have is good. If AMD had a really strong competitor they'd be doing the same, unless they're really trying to surprise Intel here, which of course would be great.I have no doubt Barcelona will be released on schedule, and I'm sure it'll outperform all Conroe setups, however I feel fairly certain that Penryn will outdo it and probably only a few months after.
Sigh...
redbone75 - Wednesday, April 18, 2007 - link
That's what I'm thinking as well. Remember back when AMD was about to release the Athlon 64 they would make all kinds of cocky comments about Intel's chips, even after purposefully delaying it a few times even though they could have released it earlier? It's because they knew what they had was going to kick some serious butt. It's not the same AMD now, and that should be cause for concern AMD supporters, unless what we're seeing is a new Intel that is now open about everything and a new AMD that is like the old Intel.TA152H - Wednesday, April 18, 2007 - link
Actually, AMD did toss out some numbers for people a few weeks ago, although they seemed inflated.It could be that the processor is clocking fairly low right now, with the 65nm manufacturing much newer to them than for Intel. Keep in mind, AMD's fastest parts for the Athlon 64, are 90nm still for now, so that indicates they don't have a great handle on 65nm right now, and of course the next processor is only being made on that. It might be more an indication of their manufacturing ability, or lack thereof, than an indictment against the processor.
That's really the crux of the problem for AMD. The P8 isn't a terribly advanced processor, much less so than the technological marvel P7, but it works much better. AMD wouldn't have terribly difficult time matching the technology in it, and probably will. But, they are always trailing in manufacturing technology and there isn't an easy way to match it. It's a big advantage for Intel too, and one that doesn't seem to be going away.
It might be, and probably will be, the Intel processors are superior for the desktop, and AMD for the servers where you have multiple sockets. It could easily come down to the design decision with regards to the location of the memory controller and the use of an FSB instead of point to point. AMD pays the price for it with one socket, Intel with multiple. Is there any mystery why AMD was showing off their server products and benchmarks, and not so forthcoming with desktop parts?
Either way, Intel is going down the same road with Nehalem although on 32nm the tradeoffs might be a lot for single socket computers.