What About The 13?

Apple's new 13-inch MacBook Pro received the biggest upgrade of the lot. Last year Apple opted against moving the 13-inch model to Arrandale and instead gave it a beefy GPU and a mildly evolved Core 2 Duo CPU. The presumed public reasoning was Apple didn't like Arrandale's GPU performance and needed a two chip solution to maintain the platform's size hence the NVIDIA GT 330M + Intel Core 2 Duo setup. Internally I'm wondering if there was a small amount of corporate politics being played there. Apple used to get a discount on Intel CPUs in exchange for exclusivity, that agreement expired with Nehalem. When Nehalem hit, Apple had to pay the same price as everyone else for CPUs. Now does the 2010 Core 2 based 13-inch MacBook Pro make more sense? Keeping Intel's flagship CPU out of Apple's highest volume MacBook Pro had to hurt. I wonder if Apple got discounted pricing on Sandy Bridge as a result...

Evolution of the 13-inch MacBook Pro Early 2011 Mid 2010 Late 2009
CPU Intel Core i5 2.3GHz (DC) Intel Core 2 Duo 2.40GHz (DC) Intel Core 2 Duo 2.26GHz (DC)
Memory 4GB DDR3-1333 4GB DDR3-1066 2GB DDR3-1066
HDD 320GB 5400RPM 250GB 5400RPM 160GB 5400RPM
Video Intel HD 3000 (integrated) NVIDIA GeForce 320M (integrated) NVIDIA GeForce 9400M (integrated)
Optical Drive 8X Slot Load DL DVD +/-R 8X Slot Load DL DVD +/-R 8X Slot Load DL DVD +/-R
Screen Resolution 1280 x 800 1280 x 800 1280 x 800
USB 2 2 2
SD Card Reader Yes Yes Yes
FireWire 800 1 1 1
ExpressCard/34 No No No
Battery 63.5Wh 63.5Wh 60Wh
Dimensions (W x D x H) 12.78" x 8.94" x 0.95" 12.78" x 8.94" x 0.95" 12.78" x 8.94" x 0.95"
Weight 4.5 lbs 4.5 lbs 4.5 lbs
Price $1199 $1199 $1199

While the 15-inch MacBook Pro is quad-core only, the new 13 is strictly dual-core. You get two options: a 2.3GHz or 2.7GHz dual-core Core i5 or Core i7. In Intel speak it's the Core i5-2410M or the Core i7-2620M (it's no wonder Apple doesn't list model numbers for these things).


The 2011 13-inch MacBook Pro Motherboard

Apple 13-inch 2011 MacBook Pro CPU Comparison
2.3GHz dual-core 2.7GHz dual-core
Intel Model Core i5-2410M Core i7-2620M
Base Clock Speed 2.3GHz 2.7GHz
Max SC Turbo 2.9GHz 3.4GHz
Max DC Turbo 2.6GHz 3.2GHz
GPU Base Clock Speed 650MHz 650MHz
GPU Max Turbo 1.2GHz 1.3GHz
L3 Cache 3MB 4MB
AES-NI No Yes
VT-x Yes Yes
VT-d No Yes
TDP 35W 35W

The primary differences between these two parts are clock speed, L3 cache size and AES-NI support once again. The 2.3GHz Core i5 lacks AES-NI, has a 3MB L3 cache and can only turbo up to 2.9GHz. The 2.7GHz Core i5 has AES-NI, a 4MB L3 cache and can turbo up as high as 3.4GHz.

I verified turbo frequencies on the 2.7GHz 13-inch. The highest I saw single core turbo hit was 3.4GHz, and dual core turbo was good for 3.2GHz. There's absolutely no funny business going on here, the dual-core 2.7 is allowed to hit its maximum frequencies.

You'll notice that the 2.7GHz DC chip has the same max single core turbo as the 2.3GHz QC chip from the upgraded 15-inch MacBook Pro. In practice this means that for light workloads the upgraded 15 won't feel any faster than the 13 (or that the 13 will feel as fast as the 15 depending on how you look at it). I'm talking about things like web page load times and application launch/install times. There may even be a slight performance advantage for the 13-inch setup as it's able to turbo up to higher frequencies easier than the quad-core 15. Crank up the threads and you've got a different story entirely of course. There's no replacement for more cores on highly threaded workloads.

Turbo and the 15-inch MacBook Pro Mostly No QuickSync
POST A COMMENT

197 Comments

View All Comments

  • IntelUser2000 - Friday, March 11, 2011 - link

    You don't know that, testing multiple systems over the years should have shown performance differences between manufacturers with identical hardware is minimal(<5%). Meaning its not Apple's fault. GPU bound doesn't mean rest of the systems woud have zero effect.

    It's not like the 2820QM is 50% faster, its 20-30% faster. The total of which could have been derived from:

    1. Quad core vs. Dual core
    2. HD3000 in the 2820QM has max clock of 1.3GHz, vs. 1.2GHz in the 2410M
    3. Clock speed of the 2820QM is quite higher in gaming scenarios
    4. LLC is shared between CPU and Graphics. 2410M has less than half the LLC of 2820QM
    5. Even at 20 fps, CPU has some impact, we're not talking 3-5 fps here

    It's quite reasonable to assume, in 3DMark03 and 05, which are explicitely single threaded, benefits from everything except #1, and frames should be high enough for CPU to affect it. Games with bigger gaps, quad core would explain to the difference, even as little as 5%.
    Reply
  • JarredWalton - Friday, March 11, 2011 - link

    I should have another dual-core SNB setup shortly, with HD 3000, so we'll be able to see how that does.

    Anyway, we're not really focusing on 3DMarks, because they're not games. Looking just at the games, there's a larger than expected gap in the performance. Remember: we've been largely GPU limited with something like the GeForce G 310M using Core i3-330UM ULV vs. Core i3-370. That's a doubling of clock speed on the CPU, and the result was: http://www.anandtech.com/bench/Product/236?vs=244 That's a 2 to 14% difference, with the exception of the heavily CPU dependent StarCraft II (which is 155% faster with the U35Jc).

    Or if you want a significantly faster GPU comparison (i.e. so the onus is on the CPU), look at the Alienware M11x R2 vs. the ASUS N82JV: http://www.anandtech.com/bench/Product/246?vs=257 Again, much faster GPU than the HD 3000 and we're only seeing 10 to 25% difference in performance for low detail gaming. At medium detail, the difference between the two platforms drops to just 0 to 15% (but it grows to 28% in BFBC2 for some reason).

    Compare that spread to the 15 to 33% difference between the i5-2415M and the i7-2820QM at low detail, and perhaps even more telling is the difference remains large at medium settings (16.7 to 44% for the i7-2820QM, except SC2 turns the tables and leads by 37%). The theoretical clock speed difference on the IGP is only 8.3%, and we're seeing two to four times that much -- the average is around 22% faster, give or take. StarCraft II is a prime example of the funkiness we're talking about: the 2820QM is 31% faster at low, but the 2415M is 37% faster at medium? That's not right....

    Whatever is going on, I can say this much: it's not just about the CPU performance potential. I'll wager than when I test the dual-core SNB Windows notebook (an ASUS model) that scores in gaming will be a lot closer than what the MBP13 managed. We'll see....
    Reply
  • IntelUser2000 - Saturday, March 19, 2011 - link

    I forgot one more thing. The quad core Sandy Bridge mobile chips support DDR3-1600 and dual core ones only up to DDR3-1333. Reply
  • mczak - Thursday, March 10, 2011 - link

    memory bus width of HD6490M and H6750M is listed as 128bit/256bit. That's quite wrong, should be 64bit/128bit.

    btw I'm wondering what's the impact on battery life for the HD6490M? It isn't THAT much faster than the HD3000, so I'm wondering if at least the power consumption isn't that much higher neither...
    Reply
  • Anand Lal Shimpi - Thursday, March 10, 2011 - link

    Thanks for the correction :)

    Take care,
    Anand
    Reply
  • gstrickler - Thursday, March 10, 2011 - link

    Anand, I would like to see heat and maximum power consumption of the 15" with the dGPU disabled using gfxCardStatus. For those of us who aren't gamers and don't need OpenCL, the dGPU is basically just a waste of power (and therefore, battery life) and a waste of money. Those should be fairly quick tests. Reply
  • Nickel020 - Thursday, March 10, 2011 - link

    The 2010 Macbooks with the Nvidia GPUs and Optimus switch to the iGPU again even if you don't close the application, right? Is this a general ATI issue that's also like this on Windows notebooks or is it only like this on OS X? This seems like quite an unnecessary hassle, actually having to manage it yourself. Not as bad as having to log off like on my late 2008 Macbook Pro, but still inconvenient. Reply
  • tipoo - Thursday, March 10, 2011 - link

    Huh? You don't have to manage it yourself. Reply
  • Nickel020 - Friday, March 11, 2011 - link

    Well if you don't want to use the dGPU when it's not necessary you kind of have to manage it yourself. If I don't want to have the dGPU power up while web browsing and make the Macbook hotter I have to manually switch to the iGPU with gfxCardStatus. I mean I can leave it set to iGPU, but then I will still manually have to switch to the dGPU when I need the dGPU. So I will have to manage it manually.

    I would really have liked to see more of a comparison with how the GPU switching works in the 2010 Macbook Pros. I mean I can look it up, but I can find most of the info in the review somewhere else too; the point of the review is kind of to have it all the info in one place, and not having to look stuff up.
    Reply
  • tajmahal42 - Friday, March 11, 2011 - link

    I think switching behaviour should be exactly the same for the 2010 and 2011 MacBook Pros, as the switching is done by the Mac OS, not by the Hardware.

    Apparently, Chrome doesn't properly close done Flash when it doesn't need it anymore or something, so the OS thinks it should still be using the dGPU.
    Reply

Log in

Don't have an account? Sign up now