Nehalem-EP......BLOOMFIELD

[Blauhung]

If speculations are right then if u clock nehalem to 4ghz then with turbo mode on it will go up to 5!
Nah....
Then it would propably crash and u would need to keep turbo mode off, in order to be always at 4...

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.

Let's be clear, when you overclock an XE Core i7, you 'll be using the Turbo max ratio as the max ratio ... YOU WILL NOT GET TURBO KICK IN WHEN YOU ARE OVERCLOCKING. Turbo IS the way you ll over clock, then, you ll be using the stock clock (133MHz) and you will increase it...
I recommand that you do not max out the Turbo ratio, and do a trade between Turbo ratio and clock increase via the base clock. This gives the best frequency results.

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.