Intel's Core i7 870 & i5 750, Lynnfield: Harder, Better, Faster Stronger
by Anand Lal Shimpi on September 8, 2009 12:00 AM EST- Posted in
- CPUs
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.
Facebook
Twitter
RSS
343 Comments
View All Comments
Scheme - Tuesday, September 8, 2009 - link
Why is it assumed enthusiasts or technical users are only interested in overclocking? For me it's about balancing performance, temps, noise levels and power consumption, all with a reasonable cost of entry. All that considered Lynnfield seems to be a good platform.Ann3x - Tuesday, September 8, 2009 - link
Well the d0 can usually hit 3.8-4ghz on std voltages.So tbh temps dont really come into it. Anyone with a 920 should overclock it because there is really nothing to lose. No need to risk the cpu, negligible temperature increases, its all positive.
If you buy a 920 and dont overclock you either should have a very good reason or you dont know how to.
The 920 is a very meh processor at stock. The reason its so popular is its potential to overclock so easily and so highly not its stock speeds.
Scheme - Tuesday, September 8, 2009 - link
3.8-4ghz will involve more than what I'd consider to be 'negligible temperature increases'.Ann3x - Tuesday, September 8, 2009 - link
I can hit 4Ghz on air with stock voltage with a max load (10hrs of LinX) of 65C. Thats so far within the thermal limits of the CPU to be considered totally negligible. My results seem very typical for d0 920s.Enthusiast CPUs need to be treated (and reviewed) in context with their market. If some people are too stupid to see the potential of their mid range CPUs then Id at least expect a good site like anandtech to realise it and not act like stock is the only option.
There is a reason why 90% of X58 motherboards are marketed on their overclock and performance options.
erple2 - Tuesday, September 8, 2009 - link
I'm a bit more interested in relatively low power consumption, and stable (as in for 4 years) operation, not how many fractional increases in performance I can eke out of a CPU at potentially catastrophic failure rates through overclocking. However, I'm buying a CPU for it's solid performance, reliability (the i7's haven't been out long enough to make any judgement of it's long term reliability), and lower power consumption. Also, can you still claim RMA status on a broken CPU that was potentially damaged by overclocking? I haven't read any Intel literature to suggest that you can.I don't care at all about what you think I my goals with buying a CPU for are. Your class of "enthusiast" is really "the overclocking user", not the "enthusiast".
I suppose it would be more interesting to find out how many of the X58 purchasers actually overclock their CPUs (beyond what "turbo" buys you), and then make conclusions, rather than this handwaving "you're an idiot if you do something other than what I do" mentality that you are showing.
I'd also like to see how many of those "90% of X58 mobos marketed on their overclock and performance options" (reference please!) are actually sold vs. those that are cheaper, and not marketed on overclocking performance. Maybe that "other 10%" sells about 40-50% of the market. Do you have data to suggest otherwise?
Ann3x - Wednesday, September 9, 2009 - link
You really think you can damage a cpu by just increasing the clock? Wow.Only things that damage CPUs are overvolting (not needed for a decent OC on the i7) and high temps (usually linked directly to overvolting). The concept that an overclock at stock voltage could cause "catastrophic failure" is frankly laughable.
A sensible overclock will be no more or less stable than stock. The only people who actually risk system stability are the ones who overvolt and push the limits. For the record 3.8-4ghz is most definitely NOT pushing the limits.
Again ill say it. If youre buying an X58 motherboard you are PAYING for the ability to overclock. If you choose not to there is little - no point in the platform (with the possible exception of people who use very multi threaded apps). The proof in this point is actually staring you in the face in the i5/new i7, their design shows that intel realises the headroom they have in the architecture. The aggressive turbo mode of the i5/new i7 is proof that there is NO risk in overclocking within sensible limits at stock voltage.
In reality the main "huge leap forward" of the new platform is simply the acceptance of overclocking within intel.
That you choose to ignore the potential of your CPU is your own loss. Intel think its safe to overclock but hey, you know better right :). Im just surprised that anand chooses to for the most part ignore this and makes absurb attention grabbing statements instead of assessing the real merits of the 2 platforms. It really is a rose tinted glasses review but oh well. Keep your heads stuck in the sand.
yacoub - Tuesday, September 8, 2009 - link
Great article except it would have been REALLY nice to have the i7 860 data, given that's most likely the best bang-for-the-buck Lynnfield option and it probably makes MUCH more sense price-wise than going for the 870. It REALLY sucks not knowing where that chip slots in for all the tests you did.This is exactly the concern I listed when the polls were posted that asked which CPU we most wanted to see benchmarked. Clearly we want to see ALL THREE.
That said, it's nice to see Lynnfield is basically awesome, except in Crossfire/SLI which is about the LAST thing I could give a crap about. So really, this looks about perfect. (Only on page 14 though, but if it continues as it has to this point, I'm sold.) I just wish the 860 had been benchmarked.
Gary Key - Tuesday, September 8, 2009 - link
I have the 860 in the upcoming mb roundups. :)yacoub - Tuesday, September 8, 2009 - link
I knew there was a reason we all love us some Gary Key. \m/. :)529th - Tuesday, September 8, 2009 - link
I'm not sure what bios setting is Sleep State on the i7 9xx (1366) but for discussions sake, say C1E sleep state is disabled, as overclockers usually do this, does that negate the logical functioning of Turbo mode and run all cores at the max TDP & speed? So would a 1366 system be faster with turbo & C1E sleep state disabled? ...i'm not even sure if i'm asking that right.. i'm still reading up on the PCU and Turbo section