Conclusion

Samsung’s Exynos 7420 is a major stepping stone for Samsung LSI. While on a functional and IP basis the chipset hasn’t seen substantial differentiation from its predecessor, it’s on the actual physical implementation and manufacturing process that the new SoC has raised the bar.

On the CPU side of things, we saw some performance improvements due to slightly higher clocks and what seems to be a better cache implementation, especially the big CPU cluster. Equally on the big cluster Samsung has played it safe and has gone for power efficiency rather than aiming for maximum achievable clocks. ARM’s Cortex A57 in the Exynos 5433 was already overshooting performance over its direct competitor, the Snapdragon 805, so there was no need for the Exynos 7420 to push the clocks much higher. And this is a good design decision for the new SoC as both maximum power as well as power efficiency have improved by a lot. With the new part now using 35-45% less power at equal frequencies it now has the required TDP and efficiency to be placed in thin smartphones such as the Galaxy S6.

I think Samsung could have even gotten away in performance benchmarks by keeping the chip at up to only 1.9GHz to keep power consumption below the 1W per core mark. This would have slightly improved efficiency on high loads as the small 10% performance degradation would have been worth the 26% power improvement.

In the review of the Exynos 5433 I was very up front about my disappointment with that SoC’s software and power management as it showed very little optimization and the degradation in real-world use-cases was measurable. This time around, it seems Samsung Electronics did a better job at properly configuring the scaling parameters of the SoC’s power management. Gone are the odd misconfigurations, and with them also most of the inefficient behaviors that we were able to measure on the big.LITTLE SoC’s predecessor. While there’s still plenty of room for improvement such as an eventual upgrade to an energy-aware scheduler, it currently does the job in a satisfactory way.

On the GPU side of things we saw sort of a two-sided story; The good side is that the Exynos 7420’s Mali T760MP8 combined with the 14nm process not only makes this the fastest SoC we’ve seen in a smartphone but also currently the most efficient one that we measured. The bad side of the story is that while it’s the most efficient SoC, the performance and power again overshoots the sustainable TDP of the phone as it will inevitably thermal throttle to lower frequency states during active usage. Over the last few generations this issue grew worse and worse as semiconductor vendors and OEMs tried to boost their competitive position in benchmark scoreboards.

While for the CPU there are real-world uses and performance advantages of having overdrive frequencies above the sustainable TDP, one cannot say the same for the GPU. Samsung is not alone here in this practice as also Qualcomm and many others employ overpowered configurations that make no sense in the devices they ship in. Having a reasonably balanced SoC has become more of the exception than the rule. One can argue that these are high-performance designs that are also meant to also go into tablets and larger form-factors, and SoC vendors should subsequently not be at the ones at receiving end of the blame – it would then be the OEM’s responsibility to properly configure and limit power via software when using the parts in smaller devices. Ultimately, I’d like to see this practice go away as it brings only disadvantages to the end-consumer and leads to an inconsistent gaming experience with reduced battery life.

The Galaxy S6 with the Exynos 7420 is among the first wave of devices to feature LPDDR4 memory. While the performance improvement was nothing ground-breaking, with the boost coming at an average 18-20% in GFXBench, it’s mostly the efficiency that should have the biggest impact on a device’s experience. While I wasn’t able to fully quantize this advantage during measurement due to the complexity of the task, the theoretical gains show that improvements in daily use-cases should be substantial.

Overall, the big question is how good the Exynos 7420 finally is. The verdict on a SoC vastly depends on the competing alternative options available at the time. For the better part of 2015 this will most likely be Qualcomm’s Snapdragon 810 and to a lesser part the Snapdragon 808. In this piece I was already able to show GPU numbers of the S810 and the results unfortunately showed no improvement over the Snapdragon 805, which the Exynos 7420 already beats both in performance and power. While I already have CPU numbers for the 810, we weren’t quite ready to include these in this piece as they’ll warrant a more in-depth look in a separate article. Readers who have already read our review of the HTC M9 will already know what to expect as the SoC just wasn’t able to perform as promised, and I can confirm that the efficiency disadvantage relative to the Exynos 7420 is significant.

Ultimately, this leaves the Exynos 7420 without real competition. Samsung was able to hit it out of the park with the new 14nm design and subsequently leapfrogged competing solutions. For the near future, the Exynos 7420 comfortably stands alone above other Android-targeted designs as it sets the new benchmark for what a 2015 SoC should be.

GPU & LPDDR4 Performance & Power
Comments Locked

114 Comments

View All Comments

  • Kepe - Monday, June 29, 2015 - link

    It's all explained right at the top of the "CPU power Consumption" page.
  • turtleman323 - Monday, June 29, 2015 - link

    I was asking for a more in-depth explanation. There are several different places a mobile device can be hooked up to for measuring CPU power -- as well as different techniques for doing so. Depending on where you instrument you will see different results. For example measuring at the battery includes the power regulator and each of the SoC subsystems has a different power domain. Also given that it's an internal battery, it is much harder to instrument than a removable battery.
  • ZeDestructor - Wednesday, July 1, 2015 - link

    Given he took apart the phone, internal battery isn' t too much of an issue, and as for wiring it iup, again, not much of an issue if you have access to a bench power supply - set it to ~3.8V DC, wire it in, and let 'er rip
  • jack1458 - Monday, June 29, 2015 - link

    Your percentage math is incorrect: going from 113 mm² to 78 mm² is a 31% shrink, not a 44% shrink. This is a classic mistake: a decrease percentage must be computed with respect to the initial quantity, not the final one.
  • name99 - Monday, June 29, 2015 - link

    "Another CCI-connected block is a new kind of IP that we haven’t seen before in the mobile space: a memory compressor. "

    My assumption, when Apple added page compression to Mavericks, was that they did the same thing to iOS7 at the same time. The internet is kinda vague on whether this happened, but I'm seeing more articles that agree than don't. Likewise it's unclear whether they used hardware for this.

    With this background, it is noteworthy that at WWDC Apple made a (reasonably) big deal about a new lossless compression library for both iOS and OSX. I take this as a signal (maybe I'm wrong) that they HAVE added a compression block to the A9 (it's a pretty obviously useful addition, after all). It's possible that there was an earlier block, but with a clumsy usage model and/or only one coded and/or other limitations; but the new block is robust enough that it can be exposed as a generic API.
  • name99 - Monday, June 29, 2015 - link

    Another way Apple could use such compression HW is in file system compression. HFS+ has had file system compression for, what, ten? years now, and while it's only used on OSX at OS installation (various system files are compressed at installation, but nothing is dynamically compressed), that's a backward compatibility issue that doesn't matter on iOS.

    Of course they could compress in SW today (and maybe they will on older devices) but HW is clearly lower power and probably faster. (And of course you can do this sort of thing at the flash controller level; but doing it higher up in the OS gives you much more power. Files that compress really small can be stuck directly in the catalog, with no allocation block at all; and already compressed files --- JPG, MP3, that sort of thing --- can be skipped over, avoiding wasting power trying to compress them further.)
  • name99 - Monday, June 29, 2015 - link

    "Apple A8
    (Typhoon)
    AArch64"

    How did you learn THIS code name? This appears to be the first mention of it on the web?
    Is Anand feeding you insider information!?

    Should we take this to mean
    (a) The A9 will be called Hurricane?
    (b) That it will not be a major revision, but basically a tweak of the A8 (same basic architecture)?
  • Andrei Frumusanu - Monday, June 29, 2015 - link

    Eh, somebody noticed :)

    The name can be seen whenever an iPhone crashes due to a kernel panic. It just took a long time to actually catch this occurrence.
  • tipoo - Tuesday, July 7, 2015 - link

    Interesting, I thought since it wasn't as big a change, it was still going by cyclone or cyclone+ or something.
  • Red Panda - Monday, June 29, 2015 - link

    Oh! they're making chips with GloFo; yield maybe an issue.

Log in

Don't have an account? Sign up now