Closing Thoughts

Wrapping things up, after Qualcomm’s experiences with the Snapdragon 810 (and to a lesser extent the 808), the company has a lot to do if they wish to recapture their grip on the high-end SoC market, and less time than they’d like to do it. What has happened with the 810 is now in the past, but to recover Qualcomm needs to show they can correct their mistakes and produce a new generation of chips as well designed as the 800/801. And they need to do so at a particularly sensitive time when customer/competitor/supplier Samsung has fully ramped up their own SoC CPU design team, which presents yet more of a challenge to Qualcomm.

As is always the case with these MDP previews, it’s critical to note that we’re looking at an early device with unoptimized software. And at the same time that we’re looking at a device and scenario where Qualcomm is looking to show off their new SoC in the best light possible. Which is to say that between now and retail devices there’s room for performance to grow and performance to shrink depending on what happens with software, thermal management, and more. However at least in the case of the Snapdragon 820 MDP/S preview, I am hopeful that our experiences here will more closely mirror retail devices since we’re looking at a phablet form factor device and not a full-size tablet has was the case in the past couple of generations.

To that end, then, Snapdragon 820 looks like Qualcomm has regained their orientation. Performance is improved over 810 – usually greatly so – at both the CPU and GPU level. And for what it’s worth, while we don’t have extensive temperature/clockspeed logs from the MDP/S, at no point did the device get hot to the touch or leave us with the impression that it was heavily throttling to avoid getting hot to the touch. Power consumption and especially efficiency (Performance/W) is clearly going to be important consideration on 820 after everyone’s experiences with 810, and while we’ll have to see what the retail devices are like, after what Samsung was able to do in their own transition from 20nm to 14nm FinFET, I feel it bodes well for Qualcomm as well.

Meanwhile more broadly speaking, our initial data doesn’t paint Snapdragon 820 as the SoC that is going to dethrone Apple’s commanding lead in ARM CPU performance. Even if retail devices improve performance, Apple A9/Twister’s performance lead in CPU-bound scenarios is extensive (particularly in lightly-threaded scenarios), more so than I’d expect any kind of software refinements to close. What seems to be rather concerning is the performance of existing software that isn't yet optimized for the new architecture, well have to see how targeted compilers for Kryo will be able to improve scores in that regard. The Adreno 530 on the other hand looks to to perform very well for a smartphone SoC, besting Apple's latest, and I think there’s a good chance for retail devices to hold their edge here.

Otherwise within the Android SoC space, the big wildcards right now are ARM’s Cortex-A72 and Samsung’s forthcoming M1 CPU. Initial performance estimates of the A72 don't put it very far from Kryo, and given that we'll be seeing some very high clocked SoCs such as the Kirin 950 at 2.3GHz or MediaTek's X20 at 2.5GHz, Qualcomm will seem to have some competition in terms of CPU performance. With the former ARM is striving for performance gains rather similar to what we’ve seen with Snapdragon 820, and Samsung's CPU is still a complete mystery at the moment. Even with their significant gains over the Snapdragon 810, if Kryo is to beat A72 and M1, then I don’t expect it will be an easy win for Qualcomm.

GPU Performance
Comments Locked

146 Comments

View All Comments

  • extide - Thursday, December 10, 2015 - link

    Dude, it has half as many cores. It's a 2+2 design vs a 4+4 design. The fact that is is able to stay close in INteger and actually win in all but one test in FP is actually really good.

    Although it kinda makes me wish they did a 3+3 design, but oh well, maybe they will in the future.
  • saratoga4 - Thursday, December 10, 2015 - link

    Got to save something for the Snapdragon 825 a year later.
  • alex3run - Friday, December 11, 2015 - link

    A9 has still worse CPU performance than Exynos 7420.
  • techconc - Wednesday, December 16, 2015 - link

    How so?
  • Thermogenic - Thursday, December 10, 2015 - link

    What I'm gathering from these charts is that every 2016 Android smartphone will have lesser performance than the 2015 iPhone, unless Samsung pulls some magic out of their hat with the next version of their chipset.
  • tuxRoller - Thursday, December 10, 2015 - link

    Yes, but so what? Apple had had better cpus for several years now. Nothing new here.
    The more interesting thing is that despite that, Android is still able to keep up with the "highly optimized" "vertically integrated" ios with flagships when it comes to everyday tasks.
  • MykeM - Thursday, December 10, 2015 - link

    http://www.xda-developers.com/marshmallow-reduces-...
  • tuxRoller - Friday, December 11, 2015 - link

    ....and? I'm aware of android's latency issues (their touch latency is...not good ether).
  • jasonelmore - Friday, December 11, 2015 - link

    what good is the performance if it's a sandboxed phone? cant carry around files on the phone, use it as portable computer with flash drive option.
  • Constructor - Saturday, December 12, 2015 - link

    That has never been true for iOS either. I've been doing that with my respective iPhones for years by now.

    There are multiple options for that, but I personally use GoodReader as my generic file system manager on my iPhone and on my iPad. I can expose my files as a mountable network drive and I can also mount remote drives as well. I can also access files on DropBox and similar services from apps directly if I want.

    This is not a real issue – nowadays it's mostly just a myth propagated among people who don't know better.

Log in

Don't have an account? Sign up now