3700 San Diego vs. 3200 Venice: Round 2!

[ben805]

Per Stephen's request, I'd completed the reruns of San Diego vs. Venice in different methodology. The previous comparison at higher speed can be found HERE




Test Configuration:

CPU1: AMD 3700 San Diego
CPU2: AMD 3200 Venice
Cooling: XP90, 90mm Enermax Fan and AS5.
RAM: GSKILL PC4800 512LA 2x256MB DDR560 @2.5-4-3-7 1T
Hard Drives: 2 x 36GB WD Raptors (RAID-0)
Motherboard: DFI LP Ultra-D
BIOS: 414-3
Video Card: MSI 6600GT
PSU: PCP&C 510 SLI
Sound Card: EMU 0404
OS: Ghost image of Windows XP Pro SP1 (fresh install with drivers only)
Target CPU speed: Both CPU at 2800 Mhz (280 x10 @1.66v)


Note: A fresh Windows XP Pro SP1 Ghost image was being use for this shootout purpose, the operating system has nothing but drivers and benchmarking softwares installed. All benchmarks were being executed in the exact same order and manner, every single test was being carry out at the exact same clock speed with the exact same memory timing, each and every single test was follow by a reboot to ensure a fresh start for the next test. Once the 3700 SD cpu has completed the task, it was then swapped out with the 3200 Venice. The BIOS setting was being left as is(exactly the same way as with the 3700 SD), once the AS5 was applied on the IHS, the exact same heatsink/fan was installed, the exact same fresh Windows XP Pro SP1 Ghost image was being restored onto the same RAID0 array, and finally follow by the exact same task again.






Disclaimer:

Warning: Overclocking is dangerous. You could easily damage your hardware components or entire system if you do not know exactly what you are doing. I am NOT responsible for what you choose to do to your own system. If you choose to overclock your system, you do so at your own risk. I am NOT affiliate with any hardware/software vendor or manufacturer in any form or way, the result that I've conducted do not represent any other (and all) Venice or San Diego, please do not rely your hardware purchase decision base on my review, as I am NOT responsible for any dud/dog/pos/sucky cpu that you might end up getting.