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

  • tajmahal - Tuesday, September 8, 2009 - link

    You fail to mention that Microcenter prices are for IN STORE PURCHASE ONLY. If you live about 6 driving hours away from a Microcenter like i do, then you're screwed.
  • Chlorus - Tuesday, September 8, 2009 - link

    Shhh! Don't spoil his self-righteous post with your troublesome facts!
  • strikeback03 - Tuesday, September 8, 2009 - link

    Does Microcenter have a limit on how many processors people can buy? If not, why isn't anyone buying these things and reselling them for less than the ~$280 that Newegg (and every other online retailer) do?
  • Solema - Tuesday, September 8, 2009 - link

    Anand,
    I know those prices you quoted are per-unit prices from Intel, but they are much more expensive than actual CPU costs. Given that I can get the following from Micro Center, and that I plan to overclock and run two 8800GTS 512's in SLI, what would you recommend?

    i5 750 - $179
    i7 920 - $199
    i7 860 - $229

    It still seems to me that the additional overclocking flexibility of the 920 (especially on stock voltage), coupled with the better multi-GPU performance would make that the best CPU to purchase, no? Given that P55 motherboards currently only retail for about $50 cheaper than many x58 boards, wouldn't the extra $70 cost for x58+i7 920 over a P55+i5 750 be worth it? You get better multi-GPU performance, better overclocking, better RAM performance, and future upgradeability to 6-core CPU's. What am I missing that would tip the scales in favor of the i5?
  • Pneumothorax - Tuesday, September 8, 2009 - link

    the 920 for sure as you get a HT CPU for even cheaper than the 860. Both should overclock the same.
  • dman - Tuesday, September 8, 2009 - link

    So, do they support Hardware Virtualization? And don't give slack about not targeted at that market, specifically, does this support Windows 7 virtualization mode?

    I searched and didn't see it covered. I've read that the i5 and lower do not support vt-d, but, I'm not sure how that translates to Windows 7 "XP mode" support... I do need to review a bit more, would be nice if this was covered in the review.

    I do know that this IS something that the Phenom family does support.

    http://www.virtualization.info/2009/07/intel-core-...">http://www.virtualization.info/2009/07/...core-i3-...

  • ash9 - Tuesday, September 8, 2009 - link

    No Virtalization!! That maybe huge for corporate setups,

    how did I miss that.

    It should have been reported
  • has407 - Wednesday, September 9, 2009 - link

    VT-x != VT-d. You want, and may need, VT-x. Most people don't need VT-d, much less know what to do with it or have a system that can make use of it--if you do, you're very unlikely to be using one of these CPUs.

    VT-x is Intel's name for processor virtualization features; it is part of the processor. All Core iX CPUs support it. VT-x is required for some hypervisors, (e.g., MSFT HYperV), but not all, although most (all?) require it for running 64-bit guests.

    VT-d is Intels name for for IO virtualization (specifically "directed IO"); it is, or has been, part of the northbridge. For VT-d to be useful, you need a chipset that supports it; a MB/BIOS that supports it; and a hypervisor that knows how to use it. VT-d is primarily of interest to VM's that want to dedicate direct access to hardware by guests, and avoid the overhead of the hypervisor for that IO.

    When you see "CPU X supports vT-d", it means the chipset for CPU X supports VT-d (the P55 supports VT-d). Whether MB/BIOS vendors choose to support it is another matter. Moreover, support for VT-d isn't simply yes or no; support varies by chipset (e.g., the P55, like the rest, support virtualizating a subset of interfaces).

    In short:

    1. Based on Core iX chipset capabilities (e.g., P55, X58), VT-d support is an MB vendor decision--not a function of the CPU model.

    2. Which vendors support VT-d, and to what extent, is more often than not clear as mud, and the topic of much discussion in some threads.

    3. If VT-d is important to you, you're probably running a heavy virtualized workload on an MP system with 10Gbe or very fast DAS--certainly not a Core iX. (Only exception of interest to others might be for access to GPU's by VMs)

    What the new processors throw into the mix is an integrated PCIe controller, which also means an integrated DMA controller (at least I hope it does). Whether that supports VT-d is unknown (I haven't been able to find a definitive answer).
  • Gary Key - Tuesday, September 8, 2009 - link

    VT-d is enabled on the i7/870-860. It is not enabled on the i5/750, just VT-x is available on it. I am working on Windows 7 XP mode as we speak.
  • Jakall78 - Tuesday, September 8, 2009 - link

    Reading this site for years, but there is something wrong going on here. Besides some slideshow pictures from Intel and 2-3 tests... there is nothing. That is not the way reviews are done. Look at the SSD reviews, THAT is a review(both of them actually). Now please look at this review
    http://translate.google.com/translate?prev=hp&...">http://translate.google.com/translate?p...mp;sl=ro...
    and say it`s not better...
    * I`m not making any false advertising here, I just found a better review.

Log in

Don't have an account? Sign up now