AMD Athlon 64 X2 6000+
Our Test Systems and SANDRA 2007
How we configured our test systems: When configuring our test systems for this article, we first entered their respective system BIOSes and set each board to its "Optimized" or "High performance Defaults". We then saved the settings, re-entered the BIOS and set memory timings for DDR2-800 with 4,4,4,12 timings. The hard drives were then formatted, and Windows XP Professional (SP2) was installed. When the Windows installation was complete, we installed the drivers necessary for our components, and removed Windows Messenger from the system. Auto-Updating and System Restore were then disabled and we set up a 1024MB permanent page file on the same partition as the Windows installation. Lastly, we set Windows XP's Visual Effects to "best performance," installed all of our benchmarking software, defragged the hard drives, and ran all of the tests.
|
System 1: AMD Athlon X2 6000+ (3.0GHz) Athlon 64 FX FX-62 (2.8GHz) Asus M2N32-SLI Deluxe (NVIDIA nForce 590 SLI)
2x1GB Corsair PC-6400 WD740 "Raptor" HD 10,000 RPM SATA Windows XP Pro SP2 nForce Drivers v9.35 NVIDIA Forceware v91.27 DirectX 9.0c |
System 2: Core 2 Extreme QX6700 (2.66Hz - Quad-Core) Core 2 Extreme X6800 / E6700 (2.93GHz & 2.66GHz)
Asus P5W DH Deluxe
2x1GB Corsair PC-6400 |
System 3: AMD Athlon 64 FX-74 AMD Athlon 64 FX-72 AMD Athlon 64 FX-70 (3.0GHz, 2.8GHz, 2.6GHz) Asus L1N64-SLI WS (NVIDIA nForce 680a SLI)
4x512MB Corsair PC-6400 WD740 "Raptor" HD 10,000 RPM SATA Windows XP Pro SP2 nForce Drivers v9.53 NVIDIA Forceware v91.27 DirectX 9.0c |
| |
Preliminary Testing with SiSoft SANDRA XI | |
Synthetic Benchmarks |
The results reported by the various SANDRA test modules fell right in line with our expectations. The Athlon 64 X2 6000+ outperformed all other AMD dual-core processors, but it couldn't quite keep up with the higher-clocked Core 2 and Xeon processors. Memory bandwidth and memory latency proved to be strong points for the CPU, as it racked up over 8.5GB/s in SANDRA's buffered memory bandwidth test, and posted the lowest latencies with block sizes up to 1MB. Once block sizes exceeded 1MB, the Core 2's larger 4MB cache allowed it to take the lead.