![2016 macbook pro 13 or 15](https://knopkazmeya.com/1.png)
That's more than the single-core score improvement from Geekbench, but nowhere near the multi-core score. The i7 saw a average of 30% speedier build times. Repeat 2 - 4 3x times to get an average.Clean, then clean build folder / delete derived data.
#2016 macbook pro 13 or 15 install
Test Process:ĭefaults write .Xcode ShowBuildOperationDuration YESīundle install -without development distribution Lastly we ran some clean builds of it using Xcode 8.1. Then we ran their setup while also turning on Xcode's build-time reporting flag so we didn't need to manually stopwatch this and introduce human error. We grabbed Artsy's app (thanks for open sourcing that, folks!) as its code-base is very real-world-app in size. Of course the real-world answer will be somewhere in between. Geekbench shows a ~20% improvement in single-core tasks, and ~70% improvement in multi-core when you go from the 2.9ghz i5 in the 13" line to the 2.7ghz i7 on the 15" line. Soroush was willing to run my test on his new 13" to compare to my results on a 15". We made sure no other processes were hogging the CPU or disk when the tests were started. Note: Geekbench links are not specific to the machines that ran the tests, but representative of the top scores for that configuration I could find. Not only does one hop CPU families with the size change (from i5 -> i7), but you're also doubling the cores (which is more important). Of more interest to me was how moving from the 13" to the 15" would effect build times. Of course, this doesn't hold a candle to what I work in when I'm at my desk on my 27" external monitor: I can actually see an entire view controller at a time without collapsing panels. I didn't think 15" would make a huge difference, but I've almost doubled my canvas area when I'm on the go. Here's a comparison of 13" vs 15" IB, in my default layout when editing a storyboard in Slopes, using the default scaling size on retina screens: Interface Builder is where I always felt the most constrained on a 13" laptop.
![2016 macbook pro 13 or 15 2016 macbook pro 13 or 15](https://www.naijatechguide.com/wp-content/uploads/2016/10/apple-macbook-pro-2016-featured-1.png)
Hopefully others might find this brief bit of information useful. So with my new MBP in-hand, and the help of some friends, I've compiled some real-world data about the differences from a developer's perspective. There were two things I wished I had better information on when shopping for a new laptop: Xcode build times, and screen real-estate while coding. Geekbench benchmarks are good indicators, but those aren't a perfect representation of real-world affects of that choice will make.Īnd it isn't like Apple lets you test out Xcode projects on floor units. It's easier to feel the difference in portability of the machines in-hand, but real-world performance is harder to judge. Part of my hangup was that of skepticism. I've always been a 13" kinda guy, erring on the side of portability, but I knew it was a tradeoff.
![2016 macbook pro 13 or 15 2016 macbook pro 13 or 15](https://i.ytimg.com/vi/QLYUpnS3YCk/maxresdefault.jpg)
One of the biggest issues I had when buying the new MacBook was what size to go with.
![2016 macbook pro 13 or 15](https://knopkazmeya.com/1.png)