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.

This is the A12, not A13

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.

The A13's Memory Subsystem: Faster L2, More SLC BW System & ML Performance


View All Comments

  • s.yu - Tuesday, October 22, 2019 - link

    Your ignorance and arrogance is hard to look at.
    I set animation speed in my 2 year old Android phone to 0.5 and most operations are now much faster.
    My 1st gen iPP is also much faster across the board with the upgrade to iPadOS, that obviously didn't upgrade the hardware.
  • Andrei Frumusanu - Tuesday, October 29, 2019 - link

    The video transcode tests in your linked videos don't even use the CPU, it's merely a hardware decoder/encoder block thing. Reply
  • d8e8fca - Saturday, November 2, 2019 - link

    The difference in SPECfp2006 scores between the A13 and the 9900k is actually a lot closer since the former includes the subscore for the 447.dealII test and the latter does not. Removing the test from the A13's score yields a value of 70.28, which is 6.5% slower. Reply
  • SirKronan - Thursday, November 7, 2019 - link

    Why do we still not have the reviews on the Samsung Note 10/10+ phones? These iPhones are still fairly hot off the press and Anand already has their very thorough review complete. I always prefer Anand's reviews of top tier phones to most other sites. This is a major letdown (that seems to indicate possible Apple bias?) to top tier phone enthusiasts. The Note 10+ isn't even on the battery comparison graph, despite representing a major battery size upgrade to Samsung's lineup. Reply
  • Andrei Frumusanu - Tuesday, November 12, 2019 - link

    We do not have the Note10's to review ; Samsung doesn't sample us.

    Given that the phones just aren't that much different to the S10's, we're unlikely to spend several thousand on purchasing the units for a review that won't have all that much new interesting information on the devices. As a note, we had to buy the S10s for that review earlier in the year.
  • willis936 - Friday, November 8, 2019 - link

    Why is there not a single word on the storage subsystem? Reply
  • Lestat1886 - Friday, December 27, 2019 - link

    « the competition in 2019 was able to push out a ton of different designs that certainly look a lot more modern than the iPhone 11 family »

    I don’t really agree, unless a pop up camera is a counted as good design innovation... and those phones don’t have any face recognition sensors... i still find the iPhone design to be among the best out there and more than competitive
  • LaDiva - Friday, January 24, 2020 - link

    Can anyone give me some feedback about the sound recording quality for iPhone11? I'm looking for something to do audition video recordings of classical singers - so acoustic quality is vitally important. I'd be very grateful for any suggestions/feedback.
  • Lucas2999 - Wednesday, February 19, 2020 - link

    I want to know how to get the MLP data of A13/A12 and other Android Platform? Simple test code writen by yourself or standard benchmark test? Reply

Log in

Don't have an account? Sign up now