The MacBook Pro Review (13 & 15-inch): 2011 Brings Sandy Bridge
by Anand Lal Shimpi, Brian Klug & Vivek Gowri on March 10, 2011 4:17 PM EST- Posted in
- Laptops
- Mac
- Apple
- Intel
- MacBook Pro
- Sandy Bridge
Performance
For our performance comparison I actually dusted off some of our 2008 8-core Mac Pro data just to show you exactly how close to a high end desktop the new quad-core MacBook Pro has come. Note that we only have comparative data for a few benchmarks so you may see the Mac Pro disappear from a few charts.
Keep in mind that the Mac Pro numbers are taken with a 3.5" hard drive (vs. the 2.5" HDD in the MBP). The big difference however is microprocessor architecture. In 2008 the Mac Pro was still running Core 2 based CPUs, while Sandy Bridge is two tocks away. What the new MBPs lack in TDP headroom and core count, they can make up for in clock speed. The result is that for the first time since I've been reviewing Apple hardware we have portable Macs that can truly hang with their desktop brethren (with some caveats of course). In order to truly bridge the mobile/desktop gap you definitely need an SSD; a 2.5" hard drive just isn't going to cut it. The Mac Pro still has a pure core count advantage. The reason I feel like the mobile/desktop gap has narrowed is because while I feel that there is a general performance benefit when going from 2 to 4 cores, it's far more difficult to find applications or usage models that take advantage of 8 or more cores.
The gap will grow once more as the iMac and Mac Pro get updated with Sandy Bridge hardware later this year, but I suspect that for even desktop users a 15-inch MacBook Pro paired with an external display may be near perfect. I believe this is a big reason for pushing Thunderbolt in this generation. While the standard may not really take off until next year, the new 15-inch MBP is definitely built for desktop replacement usage models and for that to work without sacrifice you need high speed external storage.
Adobe Photoshop CS4 Performance
The Retouch Artists Speed Test we use for our CPU testing under Windows also works under OS X. We're running the exact same benchmark here, basically performing a bunch of image manipulations and filters and timing the entire process.
Photoshop performance is just amazing on the new systems. The high end 15-inch MacBook Pro is actually faster than last year's 8-core Mac Pro. Of course this is because Photoshop doesn't scale perfectly with core count but it just shows you just how powerful these new quad-core CPUs are.
Owners of last year's 13-inch MBP will notice that the new high end 13-inch can run through our CS4 test in roughly half the time. The performance improvement is of course exaggerated because Apple kept the 13 on Core 2 for longer than it should have, but what's important is that the new 13 is really fast.
If you do a lot of Photoshop work, the Sandy Bridge upgrade will be worth it.
Aperture 2 RAW Import
For my Aperture test I simply timed how long it took to import 203 12MP RAW images into the library.
Aperture performance is similarly class leading. Here the 2010 Mac Pro actually outperforms the high end 15 by around 6% but the fact that we can even mention the two in the same sentence is huge.
The new 13 is still really quick, itself faster than a Mac Pro from as recently as 2008 in this test.
Cinebench R10 & 11.5
I’m a fan of the Cinebench tests because they lets me show off both single and multithreaded performance in the same workload. First, the single threaded performance:
Single threaded performance is really where these systems shine and it's what makes them feel so fast in normal usage. Even the base 15-inch MacBook Pro has better single threaded performance than last year's high end model.
You'll notice that the 13-inch 2.7GHz MBP has a bit of an edge compared to the 15-inch 2.3GHz system here. Although both chips can technically turbo up to 3.4GHz with only one core active, Apple seems to limit the 13-inch dual-core less. As a result it will sometimes have higher single threaded performance than the 15. I noticed this in actual usage as well. The advantage is very subtle and really only visible if you do a side to side comparison however.
Multithreaded performance is obviously a huge boon on the 15-inch MacBook Pro. With four cores and eight threads the new 15-inch MBP behaves a lot more like a desktop than a notebook. Multithreaded performance is also one area where the high end Mac Pros do a lot better as they have twice the cores of even the 15-inch MBP.
Quicktime H.264 Video Encoding
Our final benchmark is more consumer focused. Here I'm taking an XviD and converting it to an iPhone-supported H.264 format.
Despite missing Quick Sync support, the 2011 MacBook Pros do very well in our video transcoding tests. If Apple does get around to enabling Quick Sync you can expect the performance advantage to grow even more.
Facebook
Twitter
RSS
198 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%.
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....
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.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...
Anand Lal Shimpi - Thursday, March 10, 2011 - link
Thanks for the correction :)Take care,
Anand
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.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.tipoo - Thursday, March 10, 2011 - link
Huh? You don't have to manage it yourself.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.
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.