Linux Shootout: Opteron 150 vs. Xeon 3.6 Nocona
by Kristopher Kubicki on August 12, 2004 2:35 PM EST- Posted in
- Linux
John The Ripper
We are using John the Ripper 1.6.37 in this portion of the benchmark. As a few extremely knowledgeable readers pointed out, the "stable" 1.6 branch of code relies heavily on hand coded ASM which by today's standards is fairly ancient anyway. Using the "development" branch, we are able to tweak the options enough to get away from any ASM.
However, if our chess benchmarks were any indicator, optimization flags tend to skew the results dramatically. As a result, we run three trials of the John the Ripper (JTR) benchmark each using different compile flags. Configuration 1 is in the standard "make linux-x86-64" target.
- Configuration 1.) -O2
- Configuration 2.) -O3
- Configuration 3.) -O3 - march=k8 or - march=nocona
From looking at the graphs, it becomes easy to see why JTR makes a difficult program to use as a benchmark. Pay careful attention to each benchmark, particularly in between the -O2 and -O3 compile options.
OpenSSL
We couldn't think of a good way to post the OpenSSL benchmarks, so we just put both comparisons into text files which you may download here (AMD) and here (Intel). The reader is left to draw their own conclusions.
92 Comments
View All Comments
JGunther - Thursday, August 12, 2004 - link
Yeah... this reivew (to me) proves that Kris is a good, well-intentioned guy, as he put aside his own personal time to re-do these benchmarks. But the results within also prove how utterly inaccurate the first review was, thus justifying (some of) the criticism he recieved.I can see that you did learn at least one lesson, Kris; there are no claims in the conclusion of the Opteron "trouncing" the Xeon this time (even though such a remark may be justified now). :)
thatsright - Thursday, August 12, 2004 - link
Now will all of you A-Holes get off KrizK's & AT editorial staff's back!!