45nm Opteron Performance, Power Efficiency Tested
An anonymous reader writes "Now that Intel has unleashed its next-generation Core i7 processors, all eyes are turned to AMD and its incoming wave of 45nm CPUs. To get a feel for AMD's future competitiveness, The Tech Report has taken a pair of 2.7GHz 45nm Opterons (with 75W power envelopes) and put them through the paces against Intel Xeons and older, 65nm Opterons in an extensive suite of performance and power efficiency tests — from Cinema 4D and SPECjbb to computational fluid dynamics and a custom XML handling benchmark. The verdict: AMD's new 45nm quad-core design is a notable improvement over the 65nm iteration, and it proves to be a remarkably power-efficient competitor to Intel's Xeons. However, 45nm AMD chips likely don't have what it takes to best Intel's Core i7 and future Nehalem-based Xeons."
...but have since really lost momentum and competitiveness. They truly awakened the sleeping giant when they were kicking Intel's ass a few years ago.
No marketing talk in those names.
Not sure you would call it expensive, but the OPTERON chips per definition are only server chips. The Opteron 23xx series (45nm shanghai) is dual processor, while the 83xx series is quad processor.
The end user equivalent is the PHENOM series.
Note that this is a technical difference, not marketing talk. The Opterons use Socket F, while the Phenoms (single processor only) use the AM2+ socket. Different pin count, different number of interconnect ports (for connecting to other processory).
45nm Phenoms are IIRC supposed to appear soonish ;) Opterons start being available now - I pick up a new server on friday.
You should read up on the difference between dual CORE and dual PROCESSOR.
In fact, both current Opterons as well as current Phenoms are quad core systems. The Phenoms single processor (1x4 cores), the Opterons dual to quad processor (2x4 cores to 4x4 cores).
Hardly any end user system (i.e. non-server) today uses more than one processor. Dual core to quad core is normal now. But always on one processor.
The difference in sockets actually is for that - the AM2(+) socket lackss the HT bus for inter-processor communication, while the Socket F has separate lanes for the processors to talk to each other.
The main problem with Intel right now is that intel has no really nice solution at all in the multi processor side - they simply (again) do not scale from the memory side, thanks to a lack of a NUMA architecture (that they change now and coming).
I cant resist, on account of all the people who look at the Core i7 benches and think its all over; considering that the best "review" of a Nehalem EP (the dual socket variant) is a couple of guys who have a single screenshot for spec_fp, I'd say the battle's too early to call. All we've seen are single socket Nehalems-- & thats not been AMD's strong suit for some time.
Even considering that Intel's single socket game has been largely better for a while, there are some key areas AMD systems perform better. HPC, render farms, some web serving, virtualization... for all these places where people need a lot of cpus, AMD is has stayed in the runnings or maintained a lead (depends a lot on just what you're running). Unfortunately the benchmarks usually published dont factor in these kinds of workloads much at all. Cinebench is the only benchmark in the review anywhere near the above. I think if we ran some VMWare benchmarks, things would look drastically different.
But the real quesiton here is Intel: Intel is just now doing the infrastructure AMD did in early spring `03: QPI to AMD's HT, similar onboard memory setups... and thusfar aside from some spec_fp numbers, we have no idea whatsoever how well their implementation is going to work. Once Intel releases Nehalem EP for testing, we'll have an idea.
I find it disappointing that the test of the supposed server-oriented processors does not include web server tests - after all it's probably the largest market for such processors.
I mean, does anyone really care about Folding@Home number these processors can crunch? Or "VRAD map build benchmark"? WTF?
AMD didn't really destroy Itanium and then rest on their laurels. Although you have to give them some credit for coming up with reasonably good chips that the market wanted, it was more that Itanium was the reason AMD was competitive with Intel in the x86 space for a few years in the first place.
Intel has orders of magnitude more R&D budget and especially capital for fab construction than AMD does. So AMD is perpetually at least a half-generation behind Intel on the tech curve: they keep coming up with chips that could beat Intel... if they had come out a year ago. Now when Intel effectively skips a generation, as they did when they sunk all their resources into Itanium and mostly ignored x86 for a year or two, this is enough to give AMD the lead. But once Intel shifted fully back into x86, they crushed AMD again.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
You are so true about virtualization. Just 2 or 3 weeks ago I was benchmarking Linux and Windows VMs compiling Java code under Qemu/KVM-75 on an 2-socket 8-core 2.0GHz Opteron 2350 (non-Shanghai) system, and on a 1-socket 4-core 2.4GHz Core 2 Q6600 system. The VMs were configured with 1, 2, or 4 virtual processors and not more, to not give an unfair advantage to the AMD system which had twice the number of cores. Despite the lower CPU frequency as well as lower memory throughput and latency (registered DDR2-667 vs. unbuffered DDR2-800 for Intel), the AMD system was kicking the ass of the Intel system in every case by as much as 10-30%. Most likely this was because of the integrated memory controller and support of nested paging (aka "Rapid Virtualization Index"). Now Intel has cloned these 2 features in their Nehalem microarchitecture. I am very impatient to see how they perform.