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
Application Performance in Windows
by Vivek Gowri
In keeping with recent tradition, I'm in charge of evaluating the new MBP under our Windows notebook benchmark suite. Mostly, the MBP works very well as a PC, something I looked at last year with the old 13-inch MacBook Pro. I have the new base 13 in the labs, and I must say, the overall experience is pretty similar...unless you're gaming. But I'll get to that in a minute.
Unlike on the Air I was testing last time around, the Windows install went pretty smoothly thanks to the built-in optical drive. Unfortunately, that's probably going to be the last time I ever use it. And also unlike the Air, there's no problems with storage space here—with the 320GB drive included in the base 13, you have more than enough space for two moderately-sized OS install partitions.
With Windows and Boot Camp drivers out of the way, I fired up our notebook benchmark suite. The new MBP is the first dual core Sandy Bridge notebook we've had in our labs, so I was pretty interested in seeing the performance relative to Arrandale, as well as the old Core 2 Duo-based MBP13. According to CPU-Z, the base spec 13 that I have has the i5-2415M inside, a dual core processor with HyperThreading and clocked at 2.3GHz with max turbo frequency of 2.9GHz. The 2415M is an interesting chip, closely related to the i5-2410M. It's so interesting that Intel doesn't even have a product page for it, which made me curious as to what the difference between the two is. Turns out, the 2415M is the same chip as the 2410M, just in a smaller package. The normal mobile Core i5/i7 processors have a 37.5 x 37.5mm PPGA (plastic pin grid array) package, meant for Socket G2 (also known as rPGA 988B).
The 2415M, on the other hand, has a package size of 31 x 24mm with a micro-FCBGA mounting method. It's the same package size and mounting as the low voltage and ultra-low voltage Sandy Bridge processors, using the same BGA 1023 socket. Apple probably chose the 2415M to make packaging around the processor easier. Smaller is always better in the Apple world.
The other interesting wrinkle here is that Apple has forgone a separate graphics chip for the first time in a very long while. This is the first Apple with Intel graphics since the MacBook's January 2009 refresh brought Nvidia 9400M graphics, and the first MacBook Pro with Intel graphics. Ever.
What does all of this mean for performance? Let's take a look. If you're comparing to the old Core 2 Duo based MBP13, CPU-based performance is almost two times faster across the board. Given the huge jump in power between Core 2 and the further two generations of Core processors, this makes a lot of sense. It was seriously about time that Apple moved on from Core 2 in its smaller notebooks, and this huge performance jump is a direct result. We'll see what happens with the regular MacBook and MacBook Air, but I'd expect a similarly large increase in performance in those models when they're next updated as well.
Looking at the Arrandale-based Core i5-430M, which at 2.26GHz is a logical point of comparison to the i5-2415, we see that performance has improved 15-20%.
This doesn't look as impressive as the gains in performance we saw with our first look at the mobile SNB quad-cores, but Sandy Bridge quads are clocked a lot higher than the preceding Clarksfield chips. Our quad-core SNB mobile testbed had an i7-2820QM, with a 2.3GHz core clock and max turbo frequency of 3.4GHz. The 2820QM replaces the 1.86GHz i7-840QM, so the clock speed is 24% higher. Factor that in, and the increase is more in line with what we saw from the dual-cores.
The big deal here is that now, the lowest end SNB i5 performs roughly on par with the top end Arrandale i7 dual cores. Like Anand said in his Sandy Bridge review, you get yesterday's top of the line performance for a much lower price.
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.