Quote Originally Posted by Blauhung View Post
I would think the smarter way to play this would be to leave turbo mode on, and consider the multi as always n+2 when calculating what the final clock will be.

This allows you to still make use of the intelligent clock scaling up and down in periods of loading and not loading for power efficiency.

As far as reviews go. I believe that any reviewer that is looking at the platform for stock ability comparisons should leave the features to default to show consumers the out of the box performance of the platform.



And exactly, unlike the FSB, the speed of the reference clock has no direct impact on overall performance of the platform. With FSB overclocking, quite often, a lower CPU multi and higher FSB speed can hit the same CPU clock, but speed up data transfer across the bus (providing you aren't switching to a looser strap or Trd as it's called nowadays).

Here, there are no performance gains for moving the reference clock other then fine tuning CPU/Mem/QPI speeds between multipliers that fall on either side of a stability zone.
You will get more frequency on the extreme edition if you do not push too hard the frequency multipliers inside the dice. it is why you want to increase the stock clock as part of the mix. I am going into much details, but it is about clock distribution over the dice area.