Overclocking

Both the Athlon II X2 and the Phenom II X2 managed to overclock to about the same levels. Without any additional core voltage they were able to run at 3.5 - 3.6GHz, with the Athlon II being able to go a bit higher thanks to being free of any L3 cache. With less than 10% additional core voltage I was able to get both chips up to 3.7GHz. The Athlon II X2 250, when overvolted, managed to reliably hit 3.75GHz.

Gary's sample was able to work solid at 4.0GHz while mine would fail at 3.8GHz or above.

Processor Highest Overclock (Stock Voltage) Highest Overclock (Overvolted) % Increase over stock
AMD Phenom II X2 550 BE 3.5GHz 3.7GHz 19%
AMD Athlon II X2 250 3.6GHz 3.75GHz 25%
Intel Pentium E6300 3.40GHz 3.57GHz 28%

 

The Pentium E6300 topped out just under 3.6GHz with ~10% additional voltage. I noticed a strange trend when overclocking the E6300. I set the FSB to 340MHz, which when multiplied with the CPU's 10.5x multiplier should yield 3.57GHz. Yet with no additional voltage, the CPU would hardly ever go above a 10.0x multiplier once in Windows - resulting in a 3.40GHz clock speed:

The chip wasn't throttling due to heat, it simply would not run at 3.57GHz without any additional voltage. As soon as I gave it more voltage or as soon as I disabled EIST, the CPU ran at its correct frequency:


All I did was disable EIST, although increasing the VID also resulted in the same thing

Even with additional voltage however I wasn't able to get the E6300 stable at above 3.57GHz.

Processor x264 Pass 2 Cinebench XCPU Crysis Warhead
AMD Phenom II X2 550 BE @ 3.7GHz 11.0 fps 8224 74.5 fps
AMD Athlon II X2 250 @ 3.75GHz 11.0 fps 7968 75.0 fps
Intel Pentium E6300 @ 3.57GHz 11.7 fps 8096 80.8 fps

 

The Pentium E6300 is actually quite competitive when overclocked and appears to scale very well with additional clock speed. It also helps that AMD's clock speed advantage shrinks once we overclock these chips a bit.

Power Consumption Final Words
POST A COMMENT

55 Comments

View All Comments

  • adiposity - Friday, June 5, 2009 - link

    10 minutes is wrong, it's more like an hour for sub-src. My mistake. Reply
  • adiposity - Wednesday, June 3, 2009 - link

    Oh, and

    configure -release

    Will build only release target, speeds things up as well.
    Reply
  • adiposity - Wednesday, June 3, 2009 - link

    make that

    configure -release -no-webkit
    Reply
  • ssj4Gogeta - Tuesday, June 2, 2009 - link

    Anand, the x264 first pass encoding graph is "higher is better" but the processors are arranged with the shortest bar (slowest processor) on the top. Please fix that. Reply
  • Ryan Smith - Tuesday, June 2, 2009 - link

    Noted and fixed. Reply

Log in

Don't have an account? Sign up now