Linux Shootout: Opteron 150 vs. Xeon 3.6 Nocona
by Kristopher Kubicki on August 12, 2004 2:35 PM EST- Posted in
- Linux
Our preliminary look at Intel's 64-bit Xeon 3.6GHz Nocona (which happens to be identical to the Intel 3.6F Pentium 4) stirred up a bit of controversy. The largest two concerns were:
- We tested Intel's Xeon server processor against an Athlon desktop CPU.
- We chose poor benchmarks to illustrate the capabilities of those processors.
Fortunately, with the help of the other editors at AnandTech, we managed to reproduce an entire retest of the Nocona platform and an Opteron 150 CPU. We also managed to find an internet connection stable enough for this editor to redraft en entire performance analysis on his vacation.
| Performance Test Configuration | |
| Processor(s): | AMD Opteron
150 (130nm, 2.4GHz, 1MB L2 Cache) Intel Xeon 3.6GHz (90nm, 1MB L2 Cache) |
| RAM: | 2 x 512MB PC-3200 CL2 (400MHz) Registered 2 x 512MB PC2-3200 CL3 (400MHz) Registered |
| Memory Timings: | Default |
| Operating System(s): | SuSE 9.1 Professional (64 bit) Linux 2.6.4-52-default Linux 2.6.4-52-smp |
| Compiler: | linux:~ # gcc -v Reading specs from /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib64 --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit x86_64-suse-linux Thread model: posix gcc version 3.3.3 (SuSE Linux) |
| Libraries: | linux:~ # /lib/libc.so.6
GNU C Library stable release version 2.3.3
(20040405), by Roland McGrath et al.
Copyright (C) 2004 Free Software Foundation,
Inc.
This is free software; see the source for
copying conditions.
There is NO warranty; not even for MERCHANTABILITY
or FITNESS FOR A
PARTICULAR PURPOSE.
Configured for i686-suse-linux.
Compiled by GNU CC version 3.3.3 (SuSE
Linux).
Compiled on a Linux 2.6.4 system on 2004-04-05.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael
Glad and others
linuxthreads-0.10 by Xavier Leroy
GNU Libidn by Simon Josefsson
NoVersion patch for broken glibc
2.0 binaries
BIND-8.2.3-T5B
libthread_db work sponsored by
Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by
Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script
to |
The Intel Xeon 3.6GHz has HyperThreading enabled by default, so we use that
with the SMP kernel during the review. The entire review uses 64-bit binaries
either compiled from scratch or as installed from RPM. We only used a 32-bit
benchmark during the synthetic analysis, but still on SuSE 9.1 Pro (x86-64).
As one reader has pointed out, the GCC 3.3.3 used in this review has a few back ported optimizations from GCC 3.4.1 care of the SuSE development team. Thus, architecture specific optimizations for nocona are included.
Special thanks to Super Micro for getting us additional Intel components
for testing on such short notice!
Facebook
Twitter
RSS
92 Comments
View All Comments
tfranzese - Thursday, August 12, 2004 - link
Much better Kris, and I was only disappointed in not getting to see the 32-bit comparisons to see how well the current iAMD64 implementation is running.Only thing you left me confused on was the last paragraph on the John The Ripper benchmark. Might only be me who can't understand what you mean.
KristopherKubicki - Thursday, August 12, 2004 - link
datacipher:Datacipher, it really depends on your point of view. For server performance benchmarks, like the SQL stuff, another server chip was the way to go (like we did here).
If we go the desktop route, the line becomes a little blurry, particularly on Intel's end. Intel defines UP servers and high end workstations almost identically.
If we were to go on price alone, we still don't have the fairest comparison since the 150 is priced cheaper than the Xeon and the 3.6F. Some of my sources have said the 3.6F may debut considerably lower than its Xeon 3.6GHz server counterpart, even though they are the same processor with different pin outs.
Regardless of what you think, the 3.6F and Xeon 3.6GHz processors will compete against AMD dual channel offerings in the 2.4GHz range. If you read some of our other reviews, L2 cache size doesnot seem as critical on the A64 platform.
Whelp, anyway, hope that helps. When the 3.6F actually shows up at newegg with a price, then i will tell you for sure what it competes against :)
Kristopher
srg - Thursday, August 12, 2004 - link
Stellar Job on this one, you earnt the vacation. Anyway the reason this one seems more correct is that in the 32-bit tests, opteron beats the Xeon (so why should this one be so different), now everywhere else I've read are saying that the Xeon's 64-bit performance wasn't much and yours was a contradiction. That's why there was the contravercy. Anyway, this confirms the party line.srg
datacipher - Thursday, August 12, 2004 - link
Kristopher:Now I'm really confused! In the original article you say that the chips were not meant to compete...but then you also said things like "it turned out to be more appropriate than antipated". Now you are saying that since the 3.6F will be marketed against the 3500+...that it is the correct choice...
Now I'm trying to understand...forgive my ignorance. Basically you took a server chip as a stand in for the 3.6F against the 3500+ in what amounts to basically a desktop shootout? What I don't understand about this is how can Intel release a 3.6F with a roughly comparable cost to the 3500+ but with the same performance as the xeon 3.6?
Also, if the cpu choice was correct...why did you then switch to the opeteron 150?
Thanks in advance.
KristopherKubicki - Thursday, August 12, 2004 - link
Lynx516:I posted the GCC -v at the beginning of the review, please let me know if there is something else i should do.
Kristopher
KristopherKubicki - Thursday, August 12, 2004 - link
To be honest i wouldnt have known some of the mistakes i made had people not been so critical. I am not upset with the final outcome, it happens to everyone.Kristopher
Lynx516 - Thursday, August 12, 2004 - link
Sorry to be a bit harsh there Kris but they are not in the standard GCC3.3.3 manual which I was using as a reference. It would be nice to state that you are using a ported compiler in your config to prevent any future confusion. Though its a pretty good article over all. much better than some recent ones on Anand. I hope this standard is kept up.Humblest appologies
Lynx
Spectre999 - Thursday, August 12, 2004 - link
I posting because I was complaining about the first review on another board. The first review was horribly done.But it takes a real stand up person to take all the bitching that went on and be able to go back and look at what they did and decide to redo it because they made a mistake. For that I will give you much praise. The other hand is the first review shouldn't have been turned in the way it was but it isn't always the way someone does something that is the most important but the way they respond to the criticism they get.
So thanks for all the effort on redoing the article and you provided you are a stand up guy who simply made a mistake. It happens and everyone can move on.
manno - Thursday, August 12, 2004 - link
"Now will all of you A-Holes get off KrizK's & AT editorial staff's back!!"HAHHAHAHAHAHA I'm laughing my ass off.
Great Job getting in the first post, and a good first post at that.
-manno
hifisoftware - Thursday, August 12, 2004 - link
Good review. All sins are forgotten now :-)