GPU Performance

Section by Brandon Chester

Now that the general system and CPU performance of A10 Fusion has been characterized, we can move on to more focused benchmarks for the GPU and the storage subsystem. Apple's keynote for the iPhone 7 actually disclosed that the GPU in A10 Fusion is a six core part. The last time I recall Apple mentioning specifics about their GPU was with the launch of the iPad 3, where the GPU was advertised as a quad core implementation that turned out to be SGX543MP4.

The use of a six core GPU is interesting because there's not much choice for Apple given that A9 also used the six core PowerVR GT7600. It really boils down to three possibilities. The first is that Apple has actually continued using the exact same GT7600 microarchitecture as on the A9, albeit with an improved layout on the die. The second is that Apple has moved to PowerVR GT7600 Plus, which brings some improvements to integer compute performance, and memory bandwidth optimizations. And the third is the wildcard option - that Apple has put to use its significant GPU engineering resources on a more customized design; something that's still using the PowerVR architecture, but more custom than ever before. This is a longer discussion to have in our full deep dive, but Ryan's of the opinion that this is somewhere between options two and three, that Apple has done some significant work to produce a highly optimized version of the PowerVR GT7600 Plus

In any case, as Apple isn't using a radically different GPU architecture, most of Apple's stated 50% increase in GPU power comes from increasing the clock speeds, with optimizations such as memory and caching picking up the rest. This is interesting because Apple also advertises that A10 Fusion's GPU uses only two thirds the power of A9, which would indicate a lot of work done by Apple to optimize for power usage.

3DMark Sling Shot 3.1 Extreme Unlimited - Graphics

3DMark Sling Shot 3.1 Extreme Unlimited - Physics

3DMark Sling Shot 3.1 Extreme Unlimited - Overall

3DMark Sling Shot is broken down into a few different tests, and at the end the results of graphics tests and physics tests produce separate scores which are then used to generate an overall score.

In the graphics test the results are in line with Apple's stated GPU performance improvement of 50%. The physics score, which is really a CPU test, only improves by 30-35%, which has a direct correlation to the increase in peak clock speed from 1.8GHz on A9 to 2.3GHz in A10 fusion.

Like Ice Storm, the physics test is still basically a chart of devices ranked by cores multiplied by max frequency, and you can see that the iPhones have improved very little over the years, with the improvements tracking closely to Apple's increases in CPU clock speed. This comes down to the test being designed in such a way that there's little instruction level parallelism to exploit due to memory dependencies, which puts Apple's wide dual core CPU at a disadvantage. While it is certainly a valid test situation, it's not really reflective of actual 3D game performance because you would generally not write a game in such a way that it cannot exploit the performance of its target hardware.

Even with the smaller improvement in the physics tests, the overall score for the iPhone 7 is still roughly 50% higher than the Apple A9 devices like the iPhone 6s and SE.

GFXBench Manhattan ES 3.1 / Metal (On Screen)

GFXBench Manhattan ES 3.1 / Metal (Off Screen 1080p)

We originally migrated away from Manhattan ES 3.0 to Manhattan ES 3.1 / Metal to push back on devices hitting VSync in the on screen tests. Unfortunately it didn't work for long. With the iPhone 7's increase in GPU performance not being accompanied by an increase in display resolution, the on screen result in GFXBench Manhattan is higher than any other device, and is essentially at the display's refresh limit. The iPhone 7 Plus isn't able to hit Vsync due to its higher resolution, but the on screen result of roughly 42fps is nothing to scoff at either considering the visual complexity of the test.

While on screen performance is helpful from the perspective of someone who wants to see how the phone will actually perform when running a game at its native resolution, to compare directly between devices you need to standardize the rendering resolution. As its name implies, GFXBench's off screen test simply renders all the frames at 1080p in an off screen buffer. In this test the iPhone 7 and 7 Plus both run slightly below 43fps, which puts them right where you'd expect from Apple's claim of 50% greater GPU performance. In GFXBench this also puts the two of them at the same level as the 9.7" iPad Pro for absolute GPU performance.

This gives some interesting insight into the relative clock speeds that Apple is running their GPUs at, as A9X uses a twelve core PowerVR Series7XT GPU, while A10 Fusion uses only six. As I mentioned before, the performance improvements in A10 Fusion primarily come from increasing the peak clock speed. Matching the 9.7" iPad Pro's A9X suggests that Apple has targeted a fairly aggressive clock speed for the GPU in A10 Fusion, and while we can't verify Apple's claim of A10's GPU running at only two thirds the power of A9, if that is indeed the case it would represent a great deal of optimization effort on Apple's part to achieve that despite increasing clock speeds this significantly.

Storage Performance

One of the big changes that came with Apple's A9 and A9X SoCs was a new storage controller designed internally at Apple. This was not the first Apple product to use an in-house SSD controller, as the 2015 MacBook used a PCIe SSD and adopted the NVMe interface. A9 and A9X adapted this for use in mobile, and the sequentual performance in particular was far ahead of anything in a competing mobile device.

Apple hasn't advertised any improvements to storage performance with A10 Fusion, but it's worth running tests to verify that performance has remained at the same level. There are also potential gains in write performance when increasing the total capacity of an SSD by adding additional dies. At this point there's really no benchmark that can give comperable results between iOS and Android, so I've decided against doing a cross-platform comparison here.

StorageBench - Random Read

StorageBench - Random Write

StorageBench - Sequential Read

StorageBench - Sequential Write

In general, the NAND performance of the iPhone 7 and 7 Plus is equivalent to the iPhone 6s and 6s Plus. There are some minor differences, but essentially all of them can be attributed to testing variance. The only thing that is worth noting is that there's no significant improvement to write performance even though the iPhone 7 units tested are 256GB models while the 6s and 6s Plus were 128GB models. This suggests that the NAND packages use higher capacity dies so there's no additional parallelism to take advantage of.

System Performance Battery Life and Charge Time
Comments Locked

377 Comments

View All Comments

  • jlabelle2 - Tuesday, October 11, 2016 - link

    So, in a nutshell:
    - screen is very well calibrated but not in a way that makes a difference now compared to competitor, it is still not an AMOLED display and resolution is on the low side as well as maximum brightness.
    - camera is still worse than competition, even showing low light picture with twice the shutter speed, and basically the same as the 6S except a different processing (that could be given to the 6S by an over-the-air update)
    - haptic button is (obviously) worse than a physical button
    - 3,5mm jack is gone
    But it is still insanely fast, in a way that does not matter for anyone anyway because it does not offer a different experience than the 6 or 6S and still cannot overcome some small software animation issues (where the processor power is not the culprit).
    So what is exactly the appealing side of the phone versus the 6S?
  • sagarsiddhpura - Tuesday, October 11, 2016 - link

    Author is clearly biased towards iPhone. S7 does sharpening but every review states that it outperforms iP7. Photos are not well lit and just dull on iP7.
  • thek - Tuesday, October 11, 2016 - link

    the battery results do not stand with most of the other reviews I read .. (for example; http://www.trustedreviews.com/g00/iphone-7-review)...

    Now before people say that Anandtech is more technical so therefore not biased I actually think it's the exact opposite.
    It seems that anandtech relies too much on benchmarks (and I've said this in the OnePlus3 review as well) and instead of actually looking at the screen in the OP3 case or checking the real life feeling of the battery in the Iphone7 case they just say if it's bad or good based on the benchmarks.

    Personally I think that if people say that the Iphone7 battery is almost the worst they've ever had but it's excellent in the benchmarks- then I'm sure 100% Apple adjusts it's software and design to excel in benchmarks for the reviews to praise them.
    I'd feel better if Anandtech would start providing more ''real life'' feelings regarding the phones they use.
    Yes it's individual but it's becoming obvious that benchmarks are irrelevent and so does anandtech
  • thek - Tuesday, October 11, 2016 - link

    btw I'm not sure if I can post links but the bad battery life is talked about in almost every review I read. and by bad I mean not on par with other premium handsets like the galaxy s7, etc
  • rantao333@hotmail.com - Tuesday, October 11, 2016 - link

    i personally own a galaxy s6 edge and iphone 6s, under normal usage, my iphone 6s always last longer than my galaxy s6, though not by much. which ironically does not match with the result of most reviews out there.
  • Ryan Smith - Tuesday, October 11, 2016 - link

    "It seems that anandtech relies too much on benchmarks (and I've said this in the OnePlus3 review as well) and instead of actually looking at the screen in the OP3 case or checking the real life feeling of the battery in the Iphone7 case they just say if it's bad or good based on the benchmarks."

    This strikes me as an odd argument to make. You're essentially arguing against systematic testing. Which besides unscientific, is very much the opposite of how we do things. If we're going to claim that a product is good or bad, we want to have the numbers to back it up, and to ensure that it was done in a rigorous manner so that it's accurate.

    Our battery life test is specifically designed to test phones against modern webpages, piles of JS, overbearing ads, and all. It is a true workout of display, radio, and SoC, so it's very much a real life benchmark.
  • dumbnub - Tuesday, October 11, 2016 - link

    I think a more valid arguement, then ditching benchmarks, is to use benchmarks that are closer to real life. I have a huawei P9 and when I use it on wifi at home, in airplane mode, in the dark (brightness set to auto), I have yet to achieve 8hrs + like your benchmarks show. To me battery tests are most useful as a comparison between different phones rather than for accurate numbers. But I guess it's a hard task to get more accurate data because people use their phone differently and the benchmarking tools available are limited. I'm glad you do the benchmarking for battery life for comparisons sake.
  • dumbnub - Tuesday, October 11, 2016 - link

    Also reports of SOT vary wildly over at the xda developers forum for the huawei p9, so battery life is a very difficult thing to nail for everyone, maybe impossible.
  • techconc - Thursday, October 13, 2016 - link

    What matters is that the same test is being applied to all devices. The number of hours a device lasts in a test is really immaterial as the scores should still be relative to other devices tested.
  • jlabelle2 - Tuesday, October 11, 2016 - link

    The issue is not that much about relying on benchmarks, the problem is the kind of test which is done.
    Running a video for 8 hours while desactivating everything else is just completely unrealistic.
    My wife left home with her iPhone 6S at 83% at 9AM. We were traveling on the way to vacations and at noon, there was only 26% remaining. And this real life usage.

    Because: bluetooth is on (and connected to the car), push for email is activated, plenty of applications are activated and running in the background (Whatsapp, Messenger, Skype), location is on, and she is either using the phone doing some internet like facebook or it remains idle, open and close regularly along the 3 hours.
    This is real life usage. And here, you have a completely different result because you are consuming much more due to greater usage of radio module (and Apple is using a less efficient modem than other flagships as mentioned in the review), processes in the background and using the phone.

    I have never seen any iPhone (or any phone) allowing 8 hours of CONSTANT usage when everything activated and usual applications loaded. It just does not happen. And when you have a real life usage, the iPhone SIGNIFICANTLY smaller battery just cannot overcome the more efficient SoC.

Log in

Don't have an account? Sign up now