The Apple iPhone 11, 11 Pro & 11 Pro Max Review: Performance, Battery, & Camera Elevatedby Andrei Frumusanu on October 16, 2019 8:30 AM EST
SPEC2006 Perf: Desktop Levels, New Mobile Power Heights
Given that the we didn’t see too many major changes in the microarchitecture of the large Lighting CPU cores, we wouldn’t expect a particularly large performance increase over the A12. However, the 6% clock increase alongside with a few percent improvement in IPC – thanks to improvements in the memory subsystems and core front-end – could, should, and does end up delivering around a 20% performance boost, which is consistent with what Apple is advertising.
I’m still falling back to SPEC2006 for the time being as I hadn’t had time to port and test 2017 for mobile devices yet – it’s something that’s in the pipeline for the near future.
In SPECint2006, the improvements in performance are relatively evenly distributed. On average we’re seeing a 17% increase in performance. The biggest gains were had in 471.omnetpp which is latency bound, and 403.gcc which puts more pressure onto the caches; these tests saw respective increases of 25 and 24%, which is quite significant.
The 456.hmmer score increases are the lowest at 9%. That workload is highly execution backend-bound, and, given that the Lightning cores didn’t see much changes in that regard, we’re mostly seeing minor IPC increases here along with the 6% increase in clock.
While the performance figures are quite straightforward and not revealing anything surprising, the power and efficiency figures on the other hand are extremely unexpected. In virtually all of the SPECint2006 tests, Apple has gone and increased the peak power draw of the A13 SoC; and so in many cases we’re almost 1W above the A12. Here at peak performance it seems the power increase was greater than the performance increase, and that’s why in almost all workloads the A13 ends up as less efficient than the A12.
In the SPECfp2006 workloads, we’re seeing a similar story. The performance increases by the A13 are respectable and average at 19% for the suite, with individual increases between 14 and 25%.
The total power use is quite alarming here, as we’re exceeding 5W for many workloads. In 470.lbm the chip went even higher, averaging 6.27W. If I had not been actively cooling the phone and purposefully attempting it not to throttle, it would be impossible for the chip to maintain this performance for prolonged periods.
Here we saw a few workloads that were more kind in terms of efficiency, so while power consumption is still notably increased, it’s more linear with performance. However in others, we’re still seeing an efficiency regression.
Above is a more detailed historical overview of performance across the SPEC workloads and our past tested SoCs. We’ve now included the latest high-end desktop CPUs as well to give context as to where the mobile is at in terms of absolute performance.
Overall, in terms of performance, the A13 and the Lightning cores are extremely fast. In the mobile space, there’s really no competition as the A13 posts almost double the performance of the next best non-Apple SoC. The difference is a little bit less in the floating-point suite, but again we’re not expecting any proper competition for at least another 2-3 years, and Apple isn’t standing still either.
Last year I’ve noted that the A12 was margins off the best desktop CPU cores. This year, the A13 has essentially matched best that AMD and Intel have to offer – in SPECint2006 at least. In SPECfp2006 the A13 is still roughly 15% behind.
In terms of power and efficiency, the A13 seemingly wasn’t a very successful iteration for Apple, at least when it comes to the efficiency at the chip’s peak performance state. The higher power draw should mean that the SoC and phone will be more prone to throttling and sensitive to temperatures.
One possible explanation for the quite shocking power figures is that for the A13, Apple is riding the far end of the frequency/voltage curve at the peak frequencies of the new Lightning cores. In the above graph we have an estimated power curve for last year’s A12 – here we can see that Apple is very conservative with voltage up until to the last few hundred MHz. It’s possible that for the A13 Apple was even more aggressive in the later frequency states.
The good news about such a hypothesis is that the A13, on average and in daily workloads, should be operating at significantly more efficient operating points. Apple’s marketing materials describe the A13 as being 20% faster along with also stating that it uses 30% less power than the A12, which unfortunately is phrased in a deceiving (or at least unclear) manner. While we suspect that a lot of people will interpret it to mean that A13 is 20% faster while simultaneously using 30% less power, it’s actually either one or the other. In effect what this means is that at the performance point equivalent to the peak performance of the A12, the A13 would use 30% less power. Given the steepness of Apple’s power curves, I can easily imagine this to be accurate.
Nevertheless, I do question why Apple decided to be so aggressive in terms of power this generation. The N7P process node used in this generation didn’t bring any major improvements, so it’s possible they were in a tough spot of deciding between increasing power or making due with more meager performance increases. Whatever the reason, in the end it doesn’t cause any practical issues for the iPhone 11’s as the chip’s thermal management is top notch.
Post Your CommentPlease log in or sign up to comment.
View All Comments
trparky - Wednesday, October 16, 2019 - link"So while the A13 delivers class leading performance, it's probably not going to be very compelling for users coming from last year's A12 devices; the bigger impact will be felt coming from older devices."
Like no shit! I upgraded from an older iPhone 7 Plus to the iPhone 11 Pro and comparatively speaking, the iPhone 11 Pro is stupid quick (that's a good thing!!!) Everything about it is so much faster. App launch times are at least twice as fast on the iPhone 11 Pro (vs. iPhone 7 Plus) and the battery life is just... wow. I don't have words to describe how good it is on the iPhone 11 Pro when compared to the iPhone 7 Plus.
Total Meltdowner - Wednesday, October 16, 2019 - linkTwice as fast a 4 seconds is 2 seconds. Battery life of a 3600mah battery is still going to require a charge every time you make it to work or home. Bleh.
name99 - Wednesday, October 16, 2019 - linkhttps://www.youtube.com/watch?v=kqpak5lFxvs
Alistair - Wednesday, October 16, 2019 - linkDid you miss the part of the review where he showed the battery life is the best ever? Beating some 5000mah Android phones? So NO, you don't need to charge it every time you get home or back from work.
melgross - Wednesday, October 16, 2019 - linkSay what you want, but on a daily basis, it’s very noticeable. When it’s different as in 1/4 sec to 1/2 sec, come back and talk.
whiteiphoneproblems - Wednesday, October 16, 2019 - linkUnless you have a 12 hour commute, this seems pretty unlikely.
damianrobertjones - Wednesday, October 16, 2019 - linkThe mate 20 is included in the battery test, so why wouldn't the Mate 20 X also be there? Probably as it has the best battery life? Not sure.
dudedud - Wednesday, October 16, 2019 - linkHe only includes devices that he has tested.
Andrei Frumusanu - Wednesday, October 16, 2019 - linkYes, we never got our hands on the 20X.
Dragonstongue - Wednesday, October 16, 2019 - linkif Apple will slow down phone etc as battery ages, IMO they should do like SSD / HDD makers etc do by having X set aside "longevity reserve" to prevent folks from spend more $$$ to bring back new phone that using (doing normal things, let alone higher power req. stuff) chews through a not so "market leading" capacity (seeing as most phone makers and phone in general do NOT slow down / reduce performance as battery ages)
maybe just maybe they can put more "premium" into the thought/design...maybe at some point they can also do a "whitelist" for 3rd party apps etc instead of FORCED purchase / constant update crud just so can use the darn fool thing.