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.
343 Comments
View All Comments
JonnyDough - Thursday, September 10, 2009 - link
Were you purposely reiterating my point? :DI don't think AMD ever much cared about what Intel was doing. In business class I was taught to keep an eye on a competitor but to really focus on what you are doing. I think AMD was planning their next move, and it had little to do with what Intel was doing or planned on doing, but rather the reaction of what Intel would do when they created Athlon and the next step to being a successful innovative company. Going graphics was just a logical step, since NVidia had no real competition in this space. They saw a market that was ruled by two giants, and decided to combine technology. I'm not so sure that Intel had the idea first. Don't forget, there are leaks in this industry, and people are getting paid to snitch.
tajmahal - Tuesday, September 8, 2009 - link
This is the first time i've ever seen an article written using wholesale x 1,000 prices. Is there any reason you didn't take the trouble to post actual retail pricing?JonnyDough - Tuesday, September 8, 2009 - link
He probably wrote this article prior to today and based it off Intel's pricing scheme...I would think you'd probably gather that. NewEgg is also not the only E-tailer/Retailer out there...ViRGE - Tuesday, September 8, 2009 - link
The last time I checked, those are the only prices Intel gives out. The actual retail prices are a combination of what the retailer paid (buy more, spend less) and whatever markup they add. Intel doesn't have an MSRP.tajmahal - Tuesday, September 8, 2009 - link
i5 750 = $210i7 860 = $300
i7 870 = $580
Just in case someone wants to buy just 1 instead of 1,000. Newegg prices
Gary Key - Tuesday, September 8, 2009 - link
"i5 750 = $210i7 860 = $300
i7 870 = $580
Just in case someone wants to buy just 1 instead of 1,000. Newegg prices "
Retail prices fluctuate greatly at launch. This is what I paid for our retail processors with tax mind you. ;)
i5 750 = $205
i7 860 = $306
i7 870 = $564
cycleback - Tuesday, September 8, 2009 - link
Could you post some Linpack and finite element code benchmarks. This would approximate a larger number of HPC workloads. I would really appreciate this as it is difficult to find these sorts of benchmarks. It would also really test the difference in memory bandwidth between Bloomfield and Lynfield.tacoburrito - Tuesday, September 8, 2009 - link
From the benchmarks, the i7 920 and the i5 seems to be even; each winning about half the benchmarks. If costs for both are the same (proc and mobo), I think I'd still go with the 920. Of course I can stop being a cheap bastard and spring for the i7 860.tacoburrito - Tuesday, September 8, 2009 - link
I also meant to add that it should just be a matter of time before Intel cut the prices of the 920.TA152H - Tuesday, September 8, 2009 - link
One thing that's obvious is, after reading this, that the esteemed reviewer modified his review in order to fulfill his preconceived ideas of what he wanted to say. It's really a terrible review.Most people know this site isn't technical, but still, I always thought it was unbiased. It's biased, big time, just not for a company. It's about making a review say what they want.
For example, I doubt Anand is really as stupid as he sounds in this article. LGA1366 has so many advantages, certainly he knows this. But why the idiotic remarks about asking why it exists?
Why did this review ignore the fact that most people here overclock? Why did it ignore that most people reading these reviews won't use DDR3 1066 memory? Did this site just try to become PC Magazine without the writing talent, and go stock? I think not. It was because they only wanted to give information that was consistent with their preconceived idea.
But, let's look closer. The memory controller on the Bloomfield is actually faster than the Lynnfield when using the same memory, even when running in dual channel mode. Why wasn't it mentioned here?
Why wasn't a clock normalized comparison between the LGA1366 processors and LGA1156 processors made, or even attempted, to get an idea of what the architecture changes accounted for? Strange that this very important data is missing? I think so.
Why weren't overclock processors compared? I mean, will anyone here buy an i7 920 and not overclock it? Probably not many. Since the only real advantage is the more aggressive turbo mode, this was what the article was based on. But, in reality, for readers here, it's not important, since people are going to overclock, and the i7 920 would wipe the floor up with the Lynnfields in the configuration that would be used. Why no mention of this?
There are better sites that have answered these questions. I used to like this site, but this review is another disappointment.
Let's be real though, it looks like the processor's horrible performance in the pre-release configuration is just a bad memory. It's not a bad part by any stretch, but it's hardly made the LGA1366 useless, or even the i7 920. The technical savvy will still opt for it in a lot of instances, since they will overclock it. If you have to recommend something for a friend that won't, these things are fine.
Another really stupid remark was how AMD processors would only make sense if they drop the price. Have you forgotten AMD processors are coupled with excellent IGPs? That's been the big selling point for a while, and this hasn't really changed that, too much. IGP platforms are really big in sales too, so, I'd agree with the premise that AMD probably should lower their prices a little, but not that they don't have advantages even where they are. The processors don't, but you can't get an Intel motherboard with the 790GX either. And if they come out with something better, as rumored, it's just going to give their platform another advantage to help counteract their horrible processors (yes, I agree they suck).