Linux and EM64T; Intel's 64-bit Suggestion
by Kristopher Kubicki on August 9, 2004 12:05 AM EST- Posted in
- Linux
Audio Encoding
Lame was compiled from source without optimizations. We only ran ./configure and make, without any flags. We realize that some people would like to verify our binaries and sample files for their own benchmarks. In order to save bandwidth and prevent copyright infractions, we will provide our test files and binaries under limited circumstances to serious inquiries. We ran lame on a 700MB .wav file using the command equivalent to the one below:# lame sample.wav -b 192 -m s -h >/dev/null
Encoding time, lower is better.
POV-RAY
Although POV-RAY is limited in application (particularly when compared against Mental Ray), it does provide a free open source solution for basic rendering. POV-Ray 3.50c was our choice of render engine for this benchmark. For benchmark specifics, we run the exact benchmark as specified by the POV-Ray official site. We use the precompiled RPM for this test.Render Time in Seconds, less is better.
POV-Ray does not have multithread support, so we were not surprised to see the HyperThreading configuration slowing down to the configuration without HT. We see the Athlon 64 processor pull way ahead; render tasks are extremely CPU and memory dependant. With the memory controller on the CPU, Athlon 64 becomes the stronger offering in this situation.
GZip
To throw in some rudimentary tests for GZip, we used the included GZip 1.3.5 to compress the .wav file from the benchmark above. We do not want to limit our I/O on writing to the hard drive, so the operation is performed as below:# time gzip -c sample.wav > /dev/null
Intel wins their first bout of the analysis, albeit not by much. We will find a recurring pattern later on with integer based calculations and the Nocona Xeon processor. The entire Prescott family of Intel CPUs received a dedicated integer multiplier rather than continually using the floating point multiplier. This becomes extremely useful in some of our other benchmarks.
Database Performance
We will run the standard SQL-bench suite included with RPM MySQL 4.0.20d.
Of all our benchmarks, the SQL-bench becomes the most baffling. The extremely threaded database application performs particularly poorly with HyperThreading enabled. The Althon 64 outperforms Intel again in this benchmark, and a lot of it is almost certainly accredited to the on die memory controller again.
Update: We copied the 32-bit marks from our benchmark in previous testing instead of the 64-bit. You can view the previous articles here from a month ago. The graphs have also been updated.
Facebook
Twitter
RSS
275 Comments
View All Comments
fifi - Monday, August 9, 2004 - link
oh blasted, can't edit!that post above was addressed to manno.
tfranzese - Monday, August 9, 2004 - link
Edit buttons would be great, but anyway... I meant to say objective in place of subjective, but for anyone looking for someone's opinion there is also a link in there to a subjective view on Intel's implementation of AMD64.fifi - Monday, August 9, 2004 - link
why is it that it MUST be AMD-fans versus Intel-fans? can we not complain when we see shoddy work done?It's shoddy work when there's no comparison between 32-bit and 64-bit on the P4.
It's shoddy work when the benchmarks posted are simply wrong (look to his earlier review on A3500+).
No, it's not AT being bought by Intel. It's just plain shoddy work.
I would have preferred if Kristopher took his time to run the benchmarks properly, and checked all the numbers are correct and ran all the control tests and present a complete picture, rather than just trying to be the first out of the door with a review on the EM64T.
it's just plain shoddy work.
So keep on the sarcasm and hopefully it will improve your mental abilities which are clearly being impaired by the background EM waves, you SHOULD have bought those aluminium hats like I told you to...
tfranzese - Monday, August 9, 2004 - link
#55, 60, aka fanboy. Anandtech was no where the first to post Nocona benches. Not even the second, and probably not even the third.Here's some further Nocona reading which is far more informative and subjective for those interested that I've collected here: http://www.overclockersonline.com/index.php?page=w...
As for this review I can only say my respect for this site has been lowered a notch. Congrats Kris and Anand!
Viditor - Monday, August 9, 2004 - link
About what you'd expect between these 2 chips...1. 512k cache vs 1 meg cache
2. 3.6 GHs vs 2.2 GHz
3. single CPU (Opteron and Athlon64 perform much better as you add CPUs because of Hypertransport)
I really feel that this review should have been held until some comparable chips could have been tested as it appears quite biased in it's present form...
Questions though...
1. Was the setting for the memory timing on the Athlon 64 set to 1T or 2T?
2. Since both CPUs are 64bit, why use only 1 Gig of Ram? (4 Gig would have been a better demonstration...) The reason this is interesting is that there is some confusion as to Xeon's ability in handling larger amounts of memory well.
manno - Monday, August 9, 2004 - link
Oh cry me a river you poor poor souls."Alot of the benchmarks are incorrect due to setup errors. It's not just the scores that we're bitching about, but the SLOPPINESS of the review.."
Yeah it's got to be that, and not the fact that it doesn't paint AMD as the savior of the free world. Of course!! why didn't I see that the first time a lame fanboy posted?
God I feel so stupid!
You know what you're right I must of been crazy to think that Anand isn't in a secret Cabal with Intel to paint The A64 in the worst possible light. Thank you... no I truly mean it from the bottom of my heart thank you for showing me the error of my ways, and keeping evil Intel, and the even more devious Anantech.com out of my life. Well I'm going to head out now and buy myself one of those shiny aluminum hats to keep them from taking over my brain waves. Take care and have fun flaming me.
-manno
Xspringe - Monday, August 9, 2004 - link
It'd be nice to see more balanced benchmark set in the next similar review with less synthetic benchmark and more benchmarks relative to real world usage. These current benchmarks aren't very useful and incomplete as has been stated by a few people before me.hirschma - Monday, August 9, 2004 - link
I'd really love to know the sizes of the executables where the Xeon won by a significant amount. I'd bet that everything just fits in the cache for the Xeon, but not for the Athlon.If that is, in fact, the case, then Anandtech's conclusion should be: sometimes 1 meg of cache beats 512k of cache.
Sloppy, sloppy, sloppy.
WizzBall - Monday, August 9, 2004 - link
Uh you're right manno, how awful of us to not behave and thank KK for his effort... So here it is, thank you for wasting my time Kristopher!And btw, what's this bs about the 'service'... if WE wouldn't come here to read on a daily basis they would have no job, get it manno? Now go back and bow again to KK, thank you very much.
*We'll send kudos when we see something done right although it's true you can't please everybody but this time a majority of the people expressing their opinion think this is crappy work. It's weird how all the fanboys gather here on AT, huh?
Carfax - Monday, August 9, 2004 - link
Manno, have you read ANY of the replies? Alot of the benchmarks are incorrect due to setup errors. It's not just the scores that we're bitching about, but the SLOPPINESS of the review..