
First off, I should note that the Core i7 chip has what Intel calls a “turbo mode”. That is, when it’s not utilising all of its cores, it can dynamically overclock itself up to 3.4GHz on whatever single cores are in use. It can, as shown in this video, work in steps. So you get turbo benefits from partial use of the four cores in this iMac’s chip, but also, you get turbo benefits when each core is only being partially used. For example, if four cores are running but only at a fraction of their total capacity (less then 100 per cent), the cores can still run a little faster. This should theoretically make up for the difference between the two-core 3.06GHz chip and the hyper-threaded quad core chip at a base of 2.8GHz.
The other thing to realise about these newer Core i7 chips are that they have no northbridge — or bus — between the memory and CPU. The memory controller is built right into the processor, and there’s a new tech called Quickpoint interconnect which connects the cores in a point-to-point architecture. Core i7 supports triple channel memory (which would use three banks at once), but this iMac only came loaded with two banks of RAM filled. Like our other iMac, that’s a 2GB + 2GB arrangement.
Matt explains more about i7 here. (And yes, there are differences between i7 and i5, besides clock speed.)
*Note that this machine also had a faster ATI Radeon 4850 video card with 512MB of RAM (versus the 4670 card in the other iMac) which may have impacted performance in several apps. I have no idea which of these apps uses the GPU to accelerate its tasks under Snow Leopard. (For example, Preview may use it to help render JPGs faster, or it may not. Apple could not tell me. In Adobe After Effects, the Radeon series of cards apparently is not supported for OpenCL acceleration. )




In short, any task we tried that expressly was written to either a) take advantage of multiple cores, or b) take advantage of multiple cores through Snow Leopard’s multicore middleware, Grand Central Dispatch, were 2-3 times faster. (More on that here.) These results include:
• 64-bit versions of Geekbench, which focus on CPU and memory tests.
• Adobe After Effects benchmarks
• Opening 20 images of Tokyo Tower that are 2000×2000 pixels and 35MB each.
Impressive stuff, but honestly, those tests were kind of uninteresting to me. I mean, those tests don’t really have any correlation to my daily computing use. So on a whim, after benchmarking, I tested handbrake, the DVD ripping software I love. It, too, was freaking fast.





Unfortunately, there are still very few applications that take advantage of multiple cores directly or via Snow Leopard’s GCD, not even video-based, let alone general-purpose computing.
Photoshop CS4 on the Mac, which is not set up to handle multicore processors, showed almost less than a 3 per cent improvement using the Driver Heaven benchmark. Basic tasks, like booting and shutdown, saw virtually none. Playing the 1080p Quicktime trailer of Avatar consistently showed that the i7 was using 3 per cent less of its total CPU than the Core2Duo, but I wonder if that’s a result of the faster graphics card kicking in using CoreCL. Xbench, the old program that does a more comprehensive job of benchmarking a system from disks to processors, showed almost no difference.
I think Xbench, which hasn’t been updated in years, is a solid benchmark for that old program that you depend on but has been long abandoned or at least ignored by its developer.
These scores, again, are in relation to the top line 3.06GHz Core2Duo iMac we tested. Some benchmarks have come in from the web comparing the i7 to the i5. Here’s one that claims a 30 per cent jump using Geekbench. Now we know Geekbench likes and does well with more cores and is a synthetic CPU test. But if the i5 is 30 per cent slower, and the i7 pulls even with the 3.06 GHz Core2Duo chip in single threaded activity — most day-to-day activity — does that mean the i5 is slower than the cheaper Core2Duo? Maybe. Probably not 30 per cent, since Geekbench is strictly CPU/memory and likes more cores, and this stuff does not translate so literally in the real world. But we can assume the i5 will have 30 per cent less jump from the top tier Core2Duos, translating into a mere 1.3-2 times speed increase from last gen chips on programs that like cores.
For the most part, in our review, I said that you should stick to the preconfigured options, upgrading to Apple’s next recommended config before considering upgrades to the lower tier models. How does that advice change now that we’ve seen the i7? I don’t know! I guess it depends if you’re a betting man. If you think programs for Snow Leopard using GCD are coming, paying $US200-$US500 bucks more from the top line Core2Duo chip for an i5 or i7 might make sense. The probability of you getting programs that can use those extra cores goes up if you are a graphics or video professional who expects to see support from Adobe, Apple, etc. (Apple already claims big jumps in Aperture that we weren’t able to test.) Or if you rip a lot of DVDs! The rest of you? The Core2Duo stuff could be fine for today and fine for tomorrow. But the Core i7 is not worse for today and will definitely be faster tomorrow. It just costs more.
Me personally? I’d opt for the Core i7. I just might wait ’til the new iMacs refresh a bump and the i7 is cheaper and part of a standard build. But I’m patient like that.
matt
November 19, 2009 at 11:03 AM
lol, its not the more cores making up for more clock speeds.
the i7 is a brand new architecture, that shits all over c2d.
basically, 1 of the i7s cores would beat 1 of the c2d cores even tho its higher clocked.
buy the i7. don’t care how much more expensive it is, with hyper threading, it will last atleast 2 years longer than the c2d.
unless of course you need a good gfx card…
Report Permalinkadrian
November 19, 2009 at 2:08 PM
Just to point out, it’s dependent on the socket type, the I7 cpu can have either triple or dual channel architectue
(balh. i know i can’t speel. i think i’ve speelt that right)
anyway… the slocket, 1156 has no north bridge, direct memory and PCI-e interconnect, but only has Dual channel setup, and will only run 2×8 PCI-e if running 2x cards. Which is what you’ve descibed here.
The slocket 1366 has direct memory connecting, with triple channel memory, but needs a “northbridge” to control the PCI-e slots. Increasing latency to the video cards.
That said, it has the ability to run 2×16 PCI-e, (so full PCI-e v2, total 32pipes).
so, P55 v X58, P55 has less bandwidth memory bandwidth, but makes up for that with a direct connection to PCI-e. 5-10% greater frame rate on the same single video card.
Balance shifts to 5% faster on the X58 if running 2x same cards in SLI or Xfire.
Real world terms a X58 with a 920 chip and a GTX275-650mhz v P55 with 860 chip and GTX275-633mhz = same 3dmark scores, same frame rate.
(my rig = the p55, room mates = x58… BTW)
AND the difference between I7 and I5 –
Report PermalinkI7 – Quad core HT
I5 – Quad core non-HT
Stefan
November 19, 2009 at 5:06 PM
And the i7 iMax shitting over the Core 2 Duo iMac is surprising… why?
Report Permalink