Overclocked Performance

I mentioned earlier that I hit 4.6GHz on my 3960X sample, if you're curious about just how fast that makes the system have a look at this:

Overclocked: x264 HD Benchmark - 2nd pass - v3.03

The 3960X at 4.6GHz is almost twice as fast as the Core i7 2600K! The added performance does come at the expense of power consumption:

Overclocked Power Consumption - Load (x264 HD 3.03 2nd Pass)

Under load our overclocked testbed consumes 52% more power than a stock 3960X.

Power Consumption Final Words
Comments Locked

163 Comments

View All Comments

  • Phylyp - Monday, November 14, 2011 - link

    Good review, thanks. I'm researching a new gaming PC, so this review is timely. Right now, seeing the comparative performance of the 2600K vs 3960X makes me want to wait for Ivy Bridge's 2600K replacement to see what sort of VFM that offers, compared to the 3930K.
  • DaFox - Monday, November 14, 2011 - link

    > Here we see a 40% increase in performance over the 2600K and FX-1850.
    On Page 5.
  • StealthGhost - Monday, November 14, 2011 - link

    I'm guessing by these results 2600k / 2500k is going to be a much better buy for gaming vs the 3930k

    The 2600k setup (mobo/cpu) I have is, from the prices in the motherboard and CPU review, 485 dollars cheaper than a 3930k+lga2011mobo setup ($400 vs $885). More than double what I paid and while the review for that one isn't out yet, even the 3960x isn't worth double just for gaming (obviously not what it is made for but people will buy it for gaming anyways).

    I'd like to see i7 930 vs the 3930k in the review if at all possible since that is the replacement, no? Obviously 2600k as well.

    Any idea when that one will be up?
  • yankeeDDL - Monday, November 14, 2011 - link

    Tomshardware had the exact same conclusion.
    The 3960X is a workhorse and, arguably, the fastest CPU available to desktops today, however, at $999 its value is just not there.
    For a shademore than 1/2 its price you get something only marginally slower, and only in certain scenarios. Gamers, for example, have very little benefits from the extra $350 over the 3930.
  • StealthGhost - Monday, November 14, 2011 - link

    Yeah according to their review in BF3 the $999 processor would give me 0 gains since I have one card (GTX 570). If I have 2 which I might later this month it would give me 3.5 fps more, but then I wouldn't be able to afford the 2nd card in the first place haha.

    Core scaling and cache useage isn't there yet for a lot of games I guess.
  • B3an - Monday, November 14, 2011 - link

    It's pathetic that the new game engine used for BF3 dont even make use of more than 4 cores, or extra cache. And this engine is meant to be for future games... not impressed.
  • Makaveli - Monday, November 14, 2011 - link

    so why don't you design a better engine ??
  • Anand Lal Shimpi - Monday, November 14, 2011 - link

    As soon as we can get our hands on a 3930K sample :)
  • iwod - Monday, November 14, 2011 - link

    QuickSync is really for casual users only. It doesn't offer any advantage over x264 apart from the saved CPU time. x264 is faster then QuickSync with Ultrafast mode, with better quality, and much better quality with other mode then QuickSync can ever get.

    So QuickSync is good if i want to transfer my media files to my portable, where quality doesn't really matter since i have the original file backed up. It is used for convenience.

    Anyone getting a SB-E and doing encoding would properly better off with x264 then QuickSync.

    The next version of QuickSync is said to have vastly improved quality and speed.
  • Manabu - Tuesday, November 15, 2011 - link

    Intel's QuickSync quality is somewhere around x264 superfast/veryfast, for the same bitrate. Ultrafast isnt the best tradeoff for speed and quality, as it gives up everything for speed.

    But I agree, someone with an Sandy Bridge E would be better off using x264 if he learns how to.

    A good comparison on speed and quality between GPU and CPU only encoders:
    http://www.behardware.com/articles/828-1/h-264-enc...

    The only thing they missed is that, if you only care about quality, and not an specific filesize/bitrate, you should be using CRF, and not 2-pass, and much less one pass with --bitrate.

Log in

Don't have an account? Sign up now