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

  • Jamahl - Tuesday, September 8, 2009 - link

    Digusting! How much money did intel bung you for this disgrace?
  • strikeback03 - Tuesday, September 8, 2009 - link

    How is that disgusting? It is the stock configuration of the processor. They are not doing all this testing as an e-pissing contest of who has better performance per clock, it is a comparison of retail products in real-world applications. If (and according to the review, when) AMD has something similar, I'd imagine they will test with that turned on too.
  • Jamahl - Tuesday, September 8, 2009 - link

    Why not benchmark the Phenom 2 with fusion for gaming anand???
  • Gary Key - Tuesday, September 8, 2009 - link

    "Why not benchmark the Phenom 2 with fusion for gaming anand??? "

    Have you actually tried using Fusion with Windows 7 x64? It is a total mess. I will be happy to show some results with it, most will say DNF, but that might not make you happy. ;) That said, AMD is working on it, especially trying to get it to play nice with AOD.

    In the meantime, here is the current list of items to watch out for - http://game.amd.com/us-en/drivers_fusion.aspx?p=3&...">http://game.amd.com/us-en/drivers_fusion.aspx?p=3&... .
  • Jamahl - Tuesday, September 8, 2009 - link

    What? It's AMD's fault that an unreleased 64-bit os is causing issues with their software?

    How many people are using Window 7 64 bit who visit this website?
  • Gary Key - Tuesday, September 8, 2009 - link

    It is just as bad in 64-bit Vista. I imagine a fair amount of people that visit the site are using the RTM version of Win7.
  • Jamahl - Tuesday, September 8, 2009 - link

    were you benchmarking a processor at 2.66 gigahertz or a processor at 3.2 gigahertz?
  • Gary Key - Tuesday, September 8, 2009 - link

    Do you and SnakeOil live in the same house or is the IP address just that similar? LOL.. The processors were benched as they come out of the box. For Lynnfield that means turbo was on as we stated in the article and here in the comments. For Bloomfield, that also means turbo was on, just as it comes out of the retail box.

    If you check all the other reviews on the web at the main sites, everyone tested with turbo on in the primary benchmarks. So I guess you can say there is a huge conspiracy between us to actually utilize the processors as Intel intended for the users.

    Apparently, we all failed at covering it up, so congratulations on discovering the Freeturbomasons. A now not so secret fraternal organization bent on world domination through the use of turbo frequencies inside processors carrying the blue "i" logo.

    For the AMD Phenom II x4 series, they were benched with all cores enabled just as they come out of the box, even though you can disable each core in the BIOS just like you can disable turbo on the i7/i5. I guess to make things fair, we should disable the cores on the 965 BE as having that "feature" turned on is cheating.

    Anyway, thanks for making my day, I needed some much deserved laughter. :)
  • Chlorus - Tuesday, September 8, 2009 - link

    Seeing as how Fusion isn't even out yet, that would be hard to do...go troll somewhere else. What is with the idiots coming out of the woodwork on this post? You've got the standard fanboys, as well as insecure LGA-1366 owners who feel the need to defend their purchase, and insecure purchasers of 1156 products who are afraid their choice might be bested in a benchmark somewhere.
  • Roland00 - Tuesday, September 8, 2009 - link

    Would you please rerun page 9 with an overclocked 975 and the 870. I am wondering how much the difference will grow when the gpus are fed more information due to the faster cpus. Something like 3.8 to 4.0 ghz on both cpus with turbo off (a good overclock yet not in the unreasonable area)

    If you are investing 400+ dollars in gpus, and you are building it yourself you are probably going to overclock.

Log in

Don't have an account? Sign up now