iPhone to iPad: CPU Changes

Although the iPad Air uses the same A7 from the iPhone 5s (and M7 motion coprocessor), there are a few minor differences that do lead to better performance.

At a high level we’re still talking about two 64-bit Apple Cyclone cores with 128KB L1s (64KB I$ + 64KB D$) per core, a shared 1MB L2 cache and a 4MB L3 cache that services the entire SoC. Apple increased CPU frequency from 1.3GHz to 1.4GHz in the iPad Air, a mild increase but in line with what we’ve seen from previous iPad designs. That’s the first impact on performance - a 7.69% increase in CPU frequency.

The second impact on performance is something I only noticed while digging around under the hood of the A7. It seems like the implementation in the iPad Air can, for whatever reason, hold more instructions in flight (over 20% more) than the A7 in the iPhone 5s. It’s unclear to me whether the A7 in the iPad is configured any differently via firmware/microcode or if perhaps we’re looking at a slightly different revision of the core, but the delta was repeatable in my testing.

The third, and likely biggest change impacting the iPad Air’s implementation of the A7 is the additional thermal headroom afforded by the larger chassis. I’m not going to go into details on exactly what this next test does (unfortunately we’re going to occlude some of the low level work that we do in light of all of the benchmark cheating going on), but we’re looking at a curve of performance vs. time for a particularly power heavy mix of code. We’re running the same exact code on both the iPad Air and iPhone 5s here, the only real difference is the size of the chassis:

You can see the 5s throttles back its CPU frequency to about 1GHz after the 2 minute mark. The crazy thing is that until that point the 5s manages to run at full frequency without so much as a hiccup for two full minutes, running an incredibly power hungry task. Given that most iOS apps aren’t this power intensive for such a sustained period of time, iPhone 5s users should almost always see the A7 running at a full 1.3GHz. Pretty crazy.

The iPad Air by comparison shows much more controlled behavior. Early on in the test we see a 7.7% performance advantage, which lines up perfectly with the iPad Air’s 7.7% CPU frequency advantage. By the end of the test the iPhone 5s has throttled to 900MHz, while the iPad Air drops to around 1.2GHz. At this point the iPad Air’s performance advantage grows to almost 40%.

CPU Performance

I've gone through our standard set of cross-platform browser based benchmarks to place the iPad Air's performance in perspective. As I mentioned in our 5s review, I don't know that there are many (any?) applications on iOS 7 that can really take advantage of all the A7 has to offer. There's definitely a ton of headroom left in the design. What's particularly exciting is when the A7 ends up in n-1 or n-2 iOS devices and it becomes the minimum developer target going forward.

I won't go through all of the results here again, but it's safe to say that the iPad Air is the fastest ARM based tablet on the planet at this point.

SunSpider 1.0 Benchmark

SunSpider 0.9.1 Benchmark

Mozilla Kraken Benchmark (Stock Browser)

Google Octane v1

Browsermark 2.0

WebXPRT - Overall Score

 

A7 Power Consumption

I’ll get to battery life in a bit, but I’ve been curious about the dynamic range of power consumption offered by Apple’s new A7 SoC. On the one hand we’re dealing with a lower power process (28nm vs. 32nm), but on the other hand Apple’s Cyclone cores can clearly draw more power given how beefy the architecture is this round. Apple frowns upon review sample dissection so I had to turn to a less scientific method of external platform level power measurement. The fidelity of the numbers here aren’t all that great but it’s better than nothing.

For the first test I measured platform power consumption during a Kraken run:

I purposely started measuring before the benchmark so I could get an idea of idle power consumption. The iPad Air consumes roughly 72% of the idle power as the iPad 4, both running at the same brightness. Here we’re not just seeing the A7’s advantages but also things like lower display power.

Focusing on the load portion of the measurement we see that both the new iPad and old iPad consume the same total power in this test. I suspect the A7 is drawing more power than the A6X, but it’s masked by a lower power display. Given how much faster the iPad Air is, Apple’s latest tablet features far lower overall task energy than the outgoing iPad 4. This is probably both the best case scenario for the iPad Air and the most likely case as well.

For kicks I wanted to see just how much power I could get the iPad Air to draw. Here I’m looking at platform power during our mini-power-virus test from above:

How’s that for dynamic range? Almost 12W running all out, but around half that in what we’d normally consider to be a stressful CPU test. I couldn’t get any actual applications/games on the iPad Air to behave like this so the results above are purely academic (for now). A quick run through GFXBench 2.7’s T-Rex HD test confirms that even pushing the GPU won’t hit these numbers. The max I saw running T-Rex offscreen was ~6W, and turning to an actual game (Infinity Blade 3) the iPad Air pulls less than 5W.

 

An Update on Apple’s A7: It's Better Than I Thought GPU Performance
POST A COMMENT

444 Comments

View All Comments

  • algalli - Wednesday, October 30, 2013 - link

    typing error meant to say that most people have missed the IBeacon feature in IOS Reply
  • grkhetan - Wednesday, October 30, 2013 - link

    dsumanik and beautyspin: you guys have no idea what you are talking about. Anand's reviews are the some of the most objective and in-depth reviews. With your mindset -- it is clear that you hate Apple and have such a strong bias that you are not fit to be a reader of this website. Reply
  • ekotan - Wednesday, October 30, 2013 - link

    You have listed a bunch of features which would be either impossible or pointless to implement on an ARM tablet. Apple is not a company who just adds features for the sake of ticking every box, they actually care about how the device will be used and this attention to detail is a major reason why Apple users love their Apple products. Reply
  • errorr - Wednesday, October 30, 2013 - link

    NFC will never be supported by Apple. They just aren't interested. Wireless charging is an interesting idea but the design would make it the hardest engineering challenge I can imagine as the aluminum makes that a non starter. Plus if or when the ipad does wireledd charging I'm sure it'll be proprietary. Reply
  • ClemyNX - Wednesday, October 30, 2013 - link

    I truly laughed at that.
    Haptic feedback?
    NFC?
    Someone still hasn't understood that NFC is dead.
    Reply
  • darwiniandude - Wednesday, October 30, 2013 - link

    Why does the review mention frame rate drops and lack of ram then? There is polite negativity in the review where appropriate. Reply
  • steven75 - Thursday, October 31, 2013 - link

    Haptic feedback and NFC? Why would they add two technologies that are already on their way out? Reply
  • Walkop - Tuesday, November 05, 2013 - link

    I love how everyone says NFC is dead when every single credit/debit card out there has recently adopted it for pay-and-tap, and Google Wallet has been revolutionized in that it'll work regardless of carrier through NFC now. Reply
  • Djasonw - Thursday, October 31, 2013 - link

    Yes, I definitely see a need for NFC. <smh> Reply
  • whatsa - Friday, November 01, 2013 - link

    I played with the surface variable stand and that works great
    not flapping around

    but yeah I agree with the additions
    (the outdoor screen brightness to be pumped up too)
    Reply

Log in

Don't have an account? Sign up now