CPU Performance, Cont

Having taken a look at Snapdragon 820 and the Kryo CPU from an architectural perspective, let’s look at our higher level benchmarks. We’ll start as always with the web benchmarks.

Google Octane v2 (Stock Browser)

Kraken 1.1 (Stock Browser)

WebXPRT 2015 (Stock Browser)

Kraken 1.1 (Chrome/Safari/IE)

Google Octane v2  (Chrome/Safari/IE)

There are two things we can immediately take away from these results. The first is that currently Google Chrome is incredibly unoptimized for Kryo, and this is something Qualcomm was also quick to mention. We won’t wax on about this as there’s nothing to say we haven’t said before, but Chrome could certainly stand to implement optimized JS engines sooner.

Otherwise if we look at Qualcomm’s native browser, things are greatly improved. Relative to both the Exynos 7420 (A57) powered Note 5 and the Snapdragon 810 (A57) powered Mi Note Pro, the MDP/S shows a significant lead. In fact it pretty much blows past those devices in Kraken. However while it easily takes the top spot for an Android device, even with Qualcomm’s native browser the 820 isn’t going to be able to catch up to the iPhone 6s Plus and its A9 SoC.

Basemark OS II 2.0 - Overall

Basemark OS II 2.0 - System

Basemark OS II 2.0 - Memory

Basemark OS II 2.0 - Graphics

Basemark OS II 2.0 - Web

Basemark OS II 2.0 on the other hand is less consistent. The overall score again pegs the MDP/S as the best Android device, and by over 20%. However for reasons yet to be determined, the system score is still below the latest Samsung devices. Instead where the 820 shows a clear lead is with the storage (memory) score and the graphics score. In some cases it’s even beating the iPhone 6s Plus, though overall it will fall short.

PCMark - Work Performance Overall

PCMark - Web Browsing

PCMark - Video Playback

PCMark - Writing

PCMark - Photo Editing

Our final system benchmark, PCMark, once again puts the MDP/S in a good light overall, while the individual sub-tests are more widely varied. Likely owing to the same optimization issues that dogged Chrome performance, web browsing performance trails the A57 devices. Meanwhile video playback closely trails the Snapdragon 810 powered HTC One M9, and writing performance won’t quite surpass the Galaxy S6. Where the 820 MDP/S makes up for it is in the photo editing score, which is through the roof. Here Qualcomm’s development device holds a 34% performance lead over the next-fastest device, the 810/A57 based Mi Note Pro.

CPU Performance: Meet Kryo GPU Performance
Comments Locked

146 Comments

View All Comments

  • BurntMyBacon - Monday, December 14, 2015 - link

    @mmrezaie: "It is actually at best as good as A72 performances reported so far, and not even on a same node size. So what was all the reason behind research and development when you build something as good as ARM's offering."

    To be fair, Qualcomm used ARM cores for the 810 and that turn out, lets say, less than stellar. I can understand why they might want to go back to their own IP. Even if performance is the same, that doesn't mean power consumption, heat density, etc. are the same. Samsung uses ARM cores for their Exynos chips and IIRC they had to fix a problem with their cores in the past as well to get the cores up to the speed they wanted. Also, designing it yourself can be cheaper than buying the core from ARM if you are proficient enough.
  • melgross - Thursday, December 10, 2015 - link

    What happened, really, was that the Exynos chips weren't as good as the Snapdragon, and would be used in areas of the world where cost was more important that ultimate performance. The 810 wasn't used by them because it wasn't a very good chip, and it's only been recently, with the latter tape-outs, that aimed of the heating problems have been mitigated.
  • lilmoe - Friday, December 11, 2015 - link

    "Exynos chips weren't as good as the Snapdragon"

    I'm not sure when this false perception started, but that's just the fantasy of a handful of Snapdragon apologists. Exynos SoCs have ALWAYS been better than Snapdragons since their inception with the Hummingbird (GS1). Samsung has only stumbled with the Exynos 5410 (where they didn't have a "working" CCI), and less so on the 5420, and that was more like ARM's fault rather than Samsung's. Samsung later "fixed" ARM's design and moved forward with better chips than Qualcomm's offerings starting with the Exynos 5422 (except for the integrated modem part, up until recently that is).

    They sometimes ran hotter than Snapdragons but Samsung always fixes things up with updates. Apps and Games have always run better and smoother on Exynos variants (even the 5410), and they've always aged better, *especially* after patches and software updates. I can attest to that through experience, and so can many reviewers.

    Snapdragon apologists have always argued "custom ROM support". That's a very small percentage of users. Like REALLY small, to the point of irrelevance.
  • kspirit - Friday, December 11, 2015 - link

    The main reason I do prefer devices with snapdragon SoCs is because of AOSP-based ROMs. You're right, it's a very small minority, but it's still nice to have. Samsung makes A+ hardware but their software is kind of meh to me. Personal preference and all.

    But Exynos hasn't historically been a very good chipset. Sure, it beat the 810 this year and did well with heat, but there have been shortcomings on Exynos in the past.

    I remember back in the days of GS2, Exynos didn't have anything on their chipset to support notification LEDs (and even if they did, no one knew how to use them), while the same was available on Qualcomm's chips. Also, up to at least the Galaxy S4 (maybe even S5), Samsung's Exynos devices had a very seriously annoying lag between the time the home button was pressed and the screen turned on. Someone said it was because of the S-voice shortcut but it persisted on custom ROMs where S-Voice wasn't even there. It was some hardware thing.

    TL;DR: being a benchmark destroyer isn't everything.
  • Andrei Frumusanu - Saturday, December 12, 2015 - link

    Notification LEDs have absolutely nothing to so with the SoC...
  • alex3run - Saturday, December 12, 2015 - link

    Exynos 5410 wasn't really a failure just because its GPU is FAR ahead of Adreno 320 used in SD600. I was just surprised when saw how bad Adreno 320 runs real 3D games.
  • LiverpoolFC5903 - Monday, December 14, 2015 - link

    Thats nowhere near true I am afraid. The Powervr sgx 544 mp3 was beaten in almost every metric by the Adreno 320 rev.2. CPU wise the 5410 was better due to the use of higher ipc A15 cores but GPU performance was better in the Snapdragon 600, in real life as well as in most benchmarks.

    The Adreno 320 revision 2 is still relevant at around 85 Gflops, peforming better than midrangers like the Adreno 405 and Mali T760 MP2. Its almost identical in performance with the Rogue G6200 used in Mediatek's Mt6595 and Mt6795.
  • alex3run - Monday, December 21, 2015 - link

    Sorry but Adreno 320 v2 doesn't exist at all. Stop believing the delusional lies from a chinese blog.

    As I said I was just surprised how bad Adreno 320 really is. I don't mind benchmarks because it seems like Qualcomm bought most benchmark makers. Only real performance I trust. Only in real games and apps.
  • tuxRoller - Monday, December 21, 2015 - link

    How do you determine that the pvr sgx 544 is FAR ahead of the adreno 320?
    Anything reproducible?
  • V900 - Friday, December 11, 2015 - link

    Actually Samsung probably wouldn't save any money by using an Exynos SOC.

    The two divisions are independent of each other, which means that Samsung the SOC vendor charges Samsung the device vendor the same prices they charge everyone else.

    I doubt Apple would let them manufacture their CPUs if they weren't seperate divisions and had firewalls between them.

Log in

Don't have an account? Sign up now