The Lynnfield Followup: Turbo Mode and Overclocking Investigated
by Anand Lal Shimpi on September 18, 2009 12:00 AM EST- Posted in
- CPUs
GPU Limited Gaming Oddities
Scott Wasson first picked up on this anomaly in his GPU-limited FarCry 2 results at the bottom of this page. Jon Stokes pointed it out and our own Gary Key duplicated and expanded upon the results.
The situation is this: in some cases, Nehalem can go from being much faster than Phenom II, to being measurably slower within the same benchmark depending on resolution. Gary was the first to tie the issue to the GPU used. Gary found that NVIDIA GPUs appeared to behave this way on Nehalem/Phenom II while AMD GPUs didn't. In other words, NVIDIA GPUs were running faster on AMD hardware while AMD GPUs were running faster on Intel hardware. It's all very strange.
It's no surprise that Ryan and I are working on the reviews for AMD's next-generation DX11 GPUs due out before the end of September. I cloned my GPU testbed SSD and moved it over to my CPU testbeds. I then proceeded to run a subset of our GPU tests on the Core i7 920, Core i7 870, Core i5 750, Phenom II X4 965 BE and Core 2 Quad Q9450 on two different GPUs, a GeForce GTX 275 and a Radeon HD 4890.
Let's go through the results game by game, shall we?
I'll start with Gary's FarCry 2 benchmark. We're running in DX10 mode with the optimal quality defaults (latest patch) and 2X AA. Much more GPU-bound than our normal CPU gaming tests, but that's exactly what we're looking for here. The benchmark of choice is "Ranch small", it comes with the game:
So I've duplicated Gary's results. The Nehalem cores all perform about the same, the i7 920 is a bit slower thanks to lacking turbo mode it seems. But look at the Phenom II X4, it is significantly faster regardless of resolution. Now look at the same test with a Radeon HD 4890:
The Phenom II X4 965 BE advantage disappears completely. That's odd.
Next, I ran the FarCry 2 benchmark we're using for our upcoming GPU reviews. It's the Playback action demo with Ultra Quality defaults and 4X AA enabled. First on NVIDIA hardware:
The Core i7 920 falls a bit behind the other Nehalems and while the Phenom II X4 965 BE pulls ahead slightly at 2560 x 1600, the performance is generally GPU bound across the board. An unexpected result is that the Core 2 Quad Q9450 at 1680 x 1050 is actually CPU bound. There may just be a gaming reason to upgrade your CPU after all. Now let's switch to AMD hardware:
Now this is strange. The Core 2 Quad doesn't fall behind in performance, in fact it ties the Core i7 870 at 1680 x 1050. In other words, it doesn't appear to be CPU bound anymore at 1680 x 1050. Confused?
Let's keep going.
The next game I tested was Crysis Warhead. Again I ran all of the numbers in DX10 mode, this time with "Gamer" quality presets but with "Enthusiast" quality shaders. I ran the "frost" benchmark included with the initial version of the game.
All of the lines are overlapping as they should be, we're in a GPU limited situation afterall. The 870 pulls ahead slightly at the end but it's nothing to get terribly excited about.
Switch to the Radeon HD 4890 and we now have an outlier. The Core i7 920 is measurably slower than everything else at 1680 x 1050. The only change we made was the graphics card/drivers. Next.
Dawn of War II is a RTS/RPG that includes a wonderful built in benchmark. I ran with all settings maxed out in the game (including turning AA "on"):
At 1680 x 1050 we actually see some performance breakdown here. The Lynnfields are fastest, most likely due to faster turbo modes. The Core i7 920 is next on the charts, followed by the Phenom II X4 965 BE. At the bottom we have the Core 2 Quad Q9450. But at 2560 x 1600 they all converge at roughly the same point. Since many users have monitors capable of resolutions lower than 1920 x 1200 it's quite possible that the differences between these CPUs would be noticeable.
Things don't change too much as we switch graphics cards. The Phenom II X4 does a bit better with the Radeon HD 4890, but that's about the only change.
Left 4 Dead is next. All settings are maxed including Anisotropic Filtering at 16X. V-Sync is disabled and AA is set to 4X MSAA.
These numbers mostly make sense. The i7 870 is the fastest, followed by the i5 750 and the i7 920 - you have turbo to thank for that. The Phenom II is a bit slower and the Core 2 Quad is a lot slower. But by the time you hit 2560 x 1600, all roads lead to around 76 fps.
Similar behavior with ATI hardware, whew.
HAWX is a combat flight simulator that also doubles as a great DX10 benchmark. I ran the DX10 version of the game with all settings at their highest values with the exception of Ambient Occlusion, which was set to "low".
This is another one of those games where the Phenom II pulls ahead of the Nehalem processors even at a supposedly GPU-bound 2560 x 1600 resolution. The advantage isn't huge, about 7% but the Core 2 Quad gives us some indication as to what's going on. The Q9450 actually beats everything here - perhaps it's a large L2 thing? Now look at what happens with a Radeon HD 4890:
The Core 2 Quad still does better than everything else, but pretty much everything converges at the same point. The Phenom II advantage seems to disappear. So far we have HAWX and FarCry 2 exhibiting this behavior. Mental note, next benchmark please.
Our final test is Battleforge, a free to play online card based RTS. I ran with all settings maxed out:
Here we see the opposite happening - the Phenom II X4 965 BE is far slower than anything else at 1680 x 1050. As expected, all CPUs tend to converge at the same point if you crank the resolution up high enough.
Switch graphics cards and the AMD disadvantage actually disappears. It's the opposite of what we've been seeing in games like FarCry 2 and HAWX where switching to an AMD GPU causes the AMD advantage to disappear.
What can we conclude from all of this data? Not much unfortunately. There are a couple of certainties:
1) Even at relatively stressful GPU settings, 1680 x 1050 with 4X AA enabled, some games are still CPU bound. The next-generation of DX11 GPUs will make this even more true.
2) Gaming performance isn't totally clean cut between all of these CPUs. There are situations where Nehalem is faster, Penryn is faster or Phenom II is faster. The trend appears to be that Nehalem is generally the fastest, followed by Phenom II and only rarely does the Core 2 Quad end up on top.
How do I explain the odd behavior that we've seen in some of these games? Honestly, I'm not sure if there's any one explanation. What appears to happen is a perfect storm of CPU power, GPU power, GPU drivers, cache sizes, clock speeds and instruction mix. In some cases it looks to be cache related as the Core 2 and Phenom II both do very well and have a noticeably larger L2 than Nehalem, but in other cases it's much more difficult to explain by any one variable. The fact that the situation changes almost entirely when switching to ATI hardware is what makes me believe the GPU driver is playing some role in all of this.
Ultimately it's not a big (or consistent) enough of an issue to get too worked up about, but it's definitely something real and not just a figment of testbed imagination. I've shared all of my data with hopes of figuring out exactly what's going on, but as I mentioned in my Lynnfield review - not all applications/games are going to play out the same way. I'll update you if I do find anything out.
46 Comments
View All Comments
CloudFire - Saturday, September 19, 2009 - link
Actually, you're the one that's a bit confused here.If you are using Turbo mode, you do not consume more power. The chip has a TDP of 95w, and it will not exceed that under all conditions. If you are running 4 cores, then it will even distribute the power to all the cores staying at 95w.
If you are running turbo, 2 of 3 of the cores shut off, and the remaining 1 core runs at a faster speed b/c all the juice is being used in that core, all the while staying at 95w TDP.
The difference in "Turbo" and overclocking is that, Turbo stays at TDP while overclocking goes over TDP.
the zorro - Saturday, September 19, 2009 - link
that's completely wrong.turbo is just overclocking you don't have to be a rocket scientist to understand this.flipmode - Sunday, September 20, 2009 - link
Turbo is not overclocking. You clearly are a noob, or you would know what overclocking means. Here, I'll educate you: Overclocking: verb: running a computer component, such as a CPU, beyond its factory set specifications.Since Turbo is a FEATURE, and is a part of the specification of the chip, it is in no way overclocking.
MamiyaOtaru - Sunday, September 20, 2009 - link
haha lookit how wrong you are. The whole point of turbo mode is when you have something like a single threaded app that is only going to use one core. No need to have all four chugging along then is there? So three of them shut off, and the core doing the work is overclocked to take advantage of the added headroom created when the other three shut off. No more power than all four of them running at normal speed.If all four cores are working away on something, turbo mode doesn't kick in. Simple as that, but it apparently does require a rocket scientist (aka not you)
silverblue - Sunday, September 20, 2009 - link
There is actually one speed bin for all four cores (same for three).AssBall - Saturday, September 19, 2009 - link
Maybe you should actualy read some of the lynnefield articles, not all four cores are overclocked in turbo mode, sweet-tits.