Slashdot Mirror
Core Duo - Intel's Best CPU?
Bender writes "How good is Intel's Core Duo mobile processor? Good enough that Apple chose to put it in the iMac, and good enough that Intel chose to base its next generation microprocessor architecture on it. But is it already Intel's best CPU? The Tech Report has managed to snag a micro-ATX motherboard for this processor and compared the Core Duo directly to a range of mobile and desktop CPUs from AMD and Intel, including the Athlon 64 X2 and the Pentium Extreme Edition. The results are surprising. Not only is the Core Duo's performance per watt better than the rest, but they conclude that its 'outright performance is easily superior to Intel's supposed flagship desktop processor, the Pentium Extreme Edition 965.'"
I have to say the Intel Dual Core Processor is quite impressive. It's fast enough to run just about anything I throw at it, and still keep chugging, but I believe that the article negects the fact that the dual core processor runs extremely hot vs other Intel processor. My old Sony VAIO never got as hot as my MacBook Pro does, and it is something that should be considered.
This signature was left intentionally blank.
I would argue that the 8080 was. If you normalize for date/speed that is...
More reviews here and here.
The reason for going to 64-bits is to increase the amount of physical address space, not for speed. The majority of applications, especially integer, do not benefit from bigger registers and wider ALUs.
Our QA department is testing my universal application right now (AppKit based). They've recorded a 20 to 30 percent increase in performance of a 1GB MacBook Pro over a 3GB 2Ghz Dual G5 doing a particular operation (mostly mathematics based done in cross-platform C++). It's single threaded, I might add, since OpenMP isn't here yet. The *ONLY* difference in the XCode settings between the two architectures that I made was to enable SSE3 for the Intel build. I can't believe that it's that alone, of course, and suspect it's just better code gen for the Intel architecture coming out of GCC.
Actually, x86-64 does have some speed benefits over standard ia32 for smaller programs and data sets in that it doubles the number of exposed registers. Most other archs were not register starved on the 32 bit version, so going 64 bit generally slowed the system down a bit because the pointer size doubled, taking more memory bandwidth to store pointers.
Hate to say this, but there are not that many uses for 64 bit processors yet. Manufacturers do not provide 64-bit drivers for their products. The drivers that exist are buggy. To the average Joe, 64-bit is useless. He doesn't need the extra horsepower for his Internet browser or word processor. Well, unless Vista comes out.
A NYC lawyer blogs. http://www.chuangblog.com/
Yeah, they use both HDL coding and EDA (cad-like) tools to design most microprocessors. The designs are too massive to design them by placing each wire manually - they haven't done that for _several_ generations (1980s? - not sure really)
That's not to say there isn't a small army of design engineers at Intel and AMD who work with nothing but schematics - there are. Its just that most of the logic design work is done on the HDL coding level (with either VHDL, IHDL, Verilog, or some other tool). You only start dealing with schematics at a much later stage of development. Until then your designs are constantly changing and its infinitely easy/faster to change a few lines of HDL code than to re-write hundreds/thousands of wires and transistors.
I've worked at both Intel and AMD in the past and in both cases you could take the entire codebase for a processor (HDL, microcode, ROM, etc), compile it with the right HDL compiler and run the entire thing with small test programs as a simulator. Thats how much of the validation/verification work is done before they make the masks.
As for using the old code bases... That's done a lot. There's just too much complexity and too little time for them to re-write every processor from scratch. You also have countless hours invested in making sure previous designs work. If you're only doing small changes it would be hard to justfy building something from scratch since you'll have to do all of that validation work again.