Lynnfield's Turbo Mode: Up to 17% More Performance

Turbo on Bloomfield (the first Core i7) wasn't all that impressive. If you look back at our Core i7 article from last year you'll see that it's responsible for a 2 - 5% increase in performance depending on the application. All Bloomfield desktop CPUs had 130W TDPs, so each individual core had a bit more breathing room for how fast it could run. Lynnfield brings the TDP down around 27%, meaning each core gets less TDP to work with (the lower the TDP, the greater potential there is for turbo). That combined with almost a full year of improving yields on Nehalem means that Intel can be much more aggressive with Turbo on Lynnfield.

  SYSMark 2007: Overall Dawn of War II Sacred 2 World of Warcraft
Intel Core i7 870 Turbo Disabled 206 74.3 fps 84.8 fps 60.6 fps
Intel Core i7 870 Turbo Enabled 233 81.0 fps 97.4 fps 70.7 fps
% Increase from Turbo 13.1% 9.0% 14.9% 16.7%

 

Turbo on Lynnfield can yield up to an extra 17% performance depending on the application. The biggest gains will be when running one or two threads as you can see from the table below:

Max Speed Stock 4 Cores Active 3 Cores Active 2 Cores Active 1 Core Active
Intel Core i7 870 2.93GHz 3.20GHz 3.20GHz 3.46GHz 3.60GHz
Intel Core i7 860 2.80GHz 2.93GHz 2.93GHz 3.33GHz 3.46GHz
Intel Core i5 750 2.66GHz 2.80GHz 2.80GHz 3.20GHz 3.20GHz

If Intel had Turbo mode back when dual-cores first started shipping we would've never had the whole single vs. dual core debate. If you're running a single thread, this 774M transistor beast will turn off three of its cores and run its single active core at up to 3.6GHz. That's faster than the fastest Core 2 Duo on the market today.


WoW doesn't stress more than 2 cores, Turbo mode helps ensure the i7 870 is faster than Intel's fastest dual-core CPU

It's more than just individual application performance however, Lynnfield's turbo modes can kick in when just interacting with the OS or an application. Single threads, regardless of nature, can now execute at 3.6GHz instead of 2.93GHz. It's the epitomy of Intel's hurry up and get idle philosophy.

The ultimate goal is to always deliver the best performance regardless of how threaded (or not) the workload is. Buying more cores shouldn't get you lower clock speeds, just more flexibility. The top end Lynnfield is like buying a 3.46GHz dual-core processor that can also run well threaded code at 2.93GHz.

Take this one step further and imagine what happens when you have a CPU/GPU on the same package or better yet, on the same die. Need more GPU power? Underclock the CPU cores, need more CPU power? Turn off half the GPU cores. It's always availble, real-time-configurable processing power. That's the goal and Lynnfield is the first real step in that direction.

Speed Limits: Things That Will Keep Turbo Mode from Working

As awesome as it is, Turbo doesn't work 100% of the time, its usefulness varies on a number of factors including the instruction mix of active threads and processor cooling.

The actual instructions being executed by each core will determine the amount of current drawn and total TDP of the processor. For example, video encoding uses a lot of SSE instructions which in turn keep the SSE units busy on the chip; the front end remains idle and is clock gated, so power is saved there. The resulting power savings are translated into higher clock frequency. Intel tells us that video encoding should see the maximum improvement of two bins with all four cores active.

Floating point code stresses both the front end and back end of the pipe, here we should expect to see only a 133MHz increase from turbo mode if any at all. In short, you can't simply look at whether an app uses one, two or more threads. It's what the app does that matters.

There's also the issue of background threads running in the OS. Although your foreground app may only use a single thread, there are usually dozens (if not hundreds) of active threads on your system at any time. Just a few of those being scheduled on sleeping cores will wake them up and limit your max turbo frequency (Windows 7 is allegedly better at not doing this).

You can't really control the instruction mix of the apps you run or how well they're threaded, but this last point you can control: cooling. The sort-of trump all feature that you have to respect is Intel's thermal throttling. If the CPU ever gets too hot, it will automatically reduce its clock speed in order to avoid damaging the processor; this includes a clock speed increase due to turbo mode.


Lynnfield and its retail cooler

The retail cooler that ships with the Core i7 is tiny and while it's able to remove heat well enough to allow the chip to turbo up, we've seen instances where it doesn't turbo as well due to cooling issues. Just like we recommended in the Bloomfield days, an aftermarket cooler may suit you well.

Lynnfield: Made for Windows 7 (or vice versa)

Core Parking is a feature included in Windows 7 and enabled on any multi-socket machine or any system with Hyper Threading enabled (e.g. Pentium 4, Atom, Core i7). The feature looks at the performance penalty from migrating a thread from one core to another; if the fall looks too dangerous, Windows 7 won't jump - the thread will stay parked on that core.

What this fixes are a number of the situations where enabling Hyper Threading will reduce performance thanks to Windows moving a thread from a physical core to a logical core. This also helps multi-socket systems where moving a thread from one core to the next might mean moving it (and all of its data) from one memory controller to another one on an adjacent socket.

Core Parking can't help an application that manually assigns affinity to a core. We've still seen situations where HT reduces performance under Windows 7 for example with AutoCAD 2010 and World of Warcraft.

With support in the OS however, developers should have no reason to assign affinity in software - the OS is now smart enough to properly handle multi-socket and HT enabled machines.

Homework: How Turbo Mode Works Lynnfield's Un-Core: Faster Than Most Bloomfields
Comments Locked

343 Comments

View All Comments

  • strikeback03 - Tuesday, September 8, 2009 - link

    How would you have graphics then? You would be limited to the 4xPCIe off the P55 on motherboards which support it, as there are no integrated graphics (yet)
  • MX5RX7 - Tuesday, September 8, 2009 - link

    I'm not sure that CPU/GPU integration is a good thing, from a consumer standpoint. At least in the short term.

    For example, in the article you mention how the majority of modern games are GPU, not CPU limited. The current model allows us to purchase a very capable processor and pair it with a very capable GPU. Then, when the ultra competitive GPU market has provided us with a choice of parts that easily eclipse the performance of the previous generation, we either swap graphics cards for the newer model, or purchase a second now cheaper identical card and (hopefully) double our game performance with SLI or Crossfire. All without having to upgrade the rest of the platform.

    With the current model, a new graphics API requires a new graphics card. With Larrabee, it might very well require a whole new platform.

  • Ben90 - Tuesday, September 8, 2009 - link

    Yea, im really excited for Larrabee, who knows if it will be good or not... but with intel kicking ass in everything else, it will at least be interesting

    With overclocking performance seemingly being limited by the PCI-E controller, it seems like an unlocked 1156 would be pretty sweet

    All in all i gotta admit i was kinda bitter with this whole 1156 thing because i jumped on the 1336 bandwagon and it seemed that Intel was mostly just jacking off with the new socket... but this processor seems to bring a lot more innovation than i expected (just not in raw performance, still great performance though)
  • chizow - Tuesday, September 8, 2009 - link

    Was worried no one was going to properly address one of the main differences between P55 and X58, thanks for giving it a dedicated comparison. Although I would've like to have seen more games tested, it clearly indicates PCIE bandwidth becoming an issue with current generation GPUs. This will only get worst with the impending launch of RV8x0 and GT300.
  • Anand Lal Shimpi - Tuesday, September 8, 2009 - link

    PCIe bandwidth on Lynnfield is only an issue with two GPUs, with one you get the same 16 lanes as you would on X58 or AMD 790FX.

    If I had more time I would've done more games, I just wanted to focus on those that I knew scaled the best to see what the worst case scenario would be for Lynnfield.

    In the end 2 GPUs are passable (although not always ideal on Lynnfield), but 4 GPUs are out of the question.

    Take care,
    Anand
  • JumpingJack - Thursday, September 10, 2009 - link

    Anand, a few other sites have attempted SLI/Xfire work ... on in particular shows 4 GPUs having no impact at all on gaming performance in general -- well, 3 or 4 FPS, but nothing more than a few percentages over norm.

    Could your configuration with beta or just bad first release drivers be an issue?

    Jack
  • JonnyDough - Tuesday, September 8, 2009 - link

    Would it be possible to incorporate two GPU controllers onto a die instead of one or is that what they'll be doing with future procs? I would think that two controllers with a communication hub might supply the needed bandwidth of x16 + x16.
  • Comdrpopnfresh - Tuesday, September 8, 2009 - link

    with two gpu's being passable- do you foresee that applying to both two independent gpus, as well as the single dual-card gpus?
  • Ryan Smith - Tuesday, September 8, 2009 - link

    Yes. The only difference between the two is where the PCIe bridge chip is. In the former it's on the mobo, in the latter it's on the card itself.
  • Eeqmcsq - Tuesday, September 8, 2009 - link

    Talk about bringing a bazooka to a knife fight. AMD better be throwing all their innovation ideas and the kitchen sink into Bulldozer, because Intel is thoroughly out-innovating AMD right now.

Log in

Don't have an account? Sign up now