Power consumptionWe chose to check this point first by measuring the power consumption of the CPU block with a clamp meter via the ATX12V connector, which is exclusively dedicated to the CPU. With our new method we precisely measure the power needed by the CPU power supply bloc, whose efficiency is between 80 to 90%.
We took measurements in four different situations with dual core processors: advanced stand-by, which means with energy saving options activated, in stand-by without these options, in use at 50% with one session of Prime95 and then in maximum use with two sessions of Prime95. With a quad processor, the number of sessions is increased to 4.
It’s no surprise that using a VCore at 1.4V and a fabrication process of 90 nm leads to an improvement compared to the FX-62. The 6000+ is the “hungriest” processor to date. We have almost reached Intel’s record with the “Extreme Edition” Netburst dual core. The 6000+ needs even more power than the QX6700 in four sessions of Prime95.
For overclocking, we started by increasing the FSB by increments of 5 MHz and the voltage by increments of 0.025V if necessary. We also used a Scythe Infinity cooling system for this test in order not to be restricted by the CPU’s cooler. We made sure the O/Cs supported two sessions of Prime95 for 30 minutes:
As you may have noticed, we were unable to reach 3.3 GHz or 10% better than the initial frequency of the processor. With air cooling, this is already a great score for a K8 processor (the new stepping must be a great help). However, Core 2 processors are more comfortable in this area.
Tests, Supreme Commander
We will now compare these processors with other dual core processors and our usual test suite. Here are the configurations we used:
- ATI Radeon X1950 Pro / Catalyst 6.9
- 2 x 1024 MB DDR2-800 4-4-4
- 2 x Raptor 74 GB
- Windows XP SP2 French
- Socket 775 : ASUSTeK P5W DH (i975X)
- Socket AM2 : ASUSTeK M2N32-SLI Deluxe
We initially decided to integrate Supreme Commander to our processor tests in starting with this article. However, after several attempts, we realized that the game had very strange behavior with the CPU/GPU duo. We will come back to this problem in a specially dedicated article in the near future.