|
Advice Beginners BIOS Guide CPUs Links Mainboards Memory Network Storage Video/Sound Cards Contact Forum SiteMap Sponsors WebNews Home |
. | . |
Prices: Mainboards ABIT ASUS Chaintech Shuttle Soyo Tyan CPU Intel P4 2.4C-800 P4 2.6C-800 P4 2.8C-800 P4 3.0-800 P4 3.2-800 AMD AthlonXP XP 1700+ XP 2000+ XP 2400+ XP 2500+ XP 2700+ XP 3000+ XP 3200+ Athlon64 Athlon64 3200+ Athlon64 FX-51 Opteron Opteron 240 Opteron 242 Opteron 244 Opteron 246 Memory Corsair Crucial Kingston Mushkin OCZ |
LOSTCIRCUITS |
|
| Athlon XP1800+ QuantiSpeed in the Crossfire | |
| (Review by MS, October 14, 2001) |
Some Benchmark Considerations
Before going into the main part of the review, that is system configuration and performance, there are a few things that should be said about benchmarks used. The first point concerns the use of BAPCo's Sysmark2001. Sysmark2001 is a benchmark that runs several applications simultaneously forcing multithreading if it is supported by the CPU. Because the Windows(r) Media Encoder 7.0 encoder in its original form does not properly recognize the specific instruction set of the AMD Athlon XP, AMD in collaboration with Microsoft released a patch to fix this deficiency. Unfortunately, this leads to what might be claimed a violation of the licensing agreement with BAPCo because the benchmark is not running in its originally intended environment. For any reviewer, this causes the problem of getting caught between a rock and a hard place, either way you play it, one party will claim that the use of the benchmark was flawed.
So far so good, personally, a more important issue is whether the benchmark really contributes valuable information. Multithreading is certainly interesting but to be honest, in any PC, there is simply no situation thinkable where a user can input enough data to run several applications at a pace that will result in true multithreading. By extension, the same argument holds for any office application. In light of these issues, I consider office application benchmarks as somewhat irrelevant for the power user and the average person shouldn't be concerned too much anyway because no matter of which CPU can be purchased nowadays, they all have more power than anyone can claim to use in an office environment.
Another issue about benchmarks is that in order to evaluate CPU power, it is necessary to exclude bottlenecks such as I/O latencies caused by hard disk transfer. This by itself disqualifies most current ZDBop benchmarks like the different Winstone suites that are influenced more by the speed of the hard drive used than by real CPU performance. We are interested in performance here and not bottlenecks, it is easy enough to run and add the benchmarks but I feel that they might distract from more important issues. I wish to emphasize that this does not mean that we try to discredit other reviews using other benchmarks, rather, we are trying to use a somewhat different approach and provide complementary information to what has been shown elsewhere.
This, of course makes it somewhat different to come up with meaningful benchmarks, with meaningful specifying applications where a user can actually benefit from higher performance. Whoever expects reiterations of SiSoft Sandra here will be heavily disappointed. This doesn't mean that SiSoft Sandra has no merit, it certainly does but for an evaluation of a CPU and the scrutinizing of the arbitrary QuantiSpeed Architecture algorithms it is not suitable for the simple reason that I have never seen anyone benefit from higher SiSoft numbers Because of my own conception of most standard benchmarks being inadequate, recently, we have started to move to some alternative benchmarks based strictly on real life applications. For 3D games we stick with Quake3 for the time being since it is the one benchmark that favors the Pentium4. There are other benchmarks like Return To Wolfenstein that will be included shortly to give a more rounded picture.

Screenshot of the raytracing procedure after about 1/2 of the scene is rendered. The system used in this run was the Tyan Tiger MP which is visible in form of the dual render lines (each CPU renders its own part of the scene independent, very neat)
There are other benchmarks we used for internal control and sanity checks like
next page: => Test Platforms: Gigabyte GA-7DX, VIA KT266 Reference Board =>