While we hopefully have a better understanding of the SoC's underlying architecture and specifications, let's take a look at how it performs in practice. The benchmarks are performed in the performance profile unless mentioned otherwise (No mention means there was little difference between the profiles).

We start off by our usual web-tests:

SunSpider 1.0.2 Benchmark  (Chrome/Safari/IE)

Kraken 1.1 (Chrome/Safari/IE)

Google Octane v2  (Chrome/Safari/IE)

WebXPRT (Chrome/Safari/IE)

The Honor 6 performs outstandingly in our web benchmarks. It is leading all Android devices and even manages to outperform Apple's iPhone 5S in Google Octane and Mozilla's Kraken. This is a very interesting result that can be explained by one of big.LITTLE's core strengths: very low performance latency.

While traditional SoCs will try to scale the CPU frequency up while analysing a sample period of most often 50-100ms, while taking additional time to reach the maximum P-state, the GTS controlled Kirin 920 is able to do this at a maximum latency of only 26ms from idling, and in a best case scenario <16ms if the big cluster is already on a high frequency. The task at hand gets a higher residency time at full performance over traditional DVFS mechanics. Small and spiky loads such as Javascript test benches and web-page rendering are a perfect fit for big.LITTLE's design.

It is also to be noted that Cortex A15 SoCs have generally always performed very high on the web tests, the Exynos 5410 in the international Galaxy S4 was the first A15 design found in a smartphone and was able to achieve very similar scores when locked at high frequency. There is definitely also an architecture advantage to be found here in comparison to Krait based SoCs from Qualcomm.

BaseMark OS II - Web

BaseMark OS II - System

We see a similar picture in the CPU-intensive loads of BaseMark OS II - the Kirin 920 is able to outperform all other Android devices, but still lags behind the year old Apple A7.

BaseMark OS II - Graphics

BaseMark OS II - Memory

 

BaseMark OS II - Overall

In the end, the abysmal graphics score of the Mali T628MP4 drags the final overall score on BaseMark OS.

3DMark 1.2 Unlimited - Physics

The physics test of 3DMark 1.2 Unlimited which is mainly CPU-bound sees a huge difference between the smart and performance profiles of the device. Because this is a rate-limited CPU benchmark and its load is evenly spread out over time, it provides a perfect case for lowering the HMP parameters and enabling the scheduler to migrate the process over to a big core. This is the largest delta I've been able to measure between the two main profiles that the Honor 6 provides.

Next, let's investigate the GPU performance in more detail.

Kirin 920 SoC & Platform power analysis GPU performance
Comments Locked

59 Comments

View All Comments

  • DIYEyal - Saturday, September 13, 2014 - link

    I found a typo in the battery life page: "I think this is due the phone having quite good thermal dissipation charateristics ."
  • akshayprbhu - Friday, October 10, 2014 - link

    that is not a typo. The phone is having good thermal dissipation as it is cooler than similar spec phones when a performance test was done! Youtube for more proof...
  • lilmoe - Saturday, September 13, 2014 - link

    Great review of what really matters. I especially liked the in-depth analysis of the SoC and its platform power in comparison to others. Looking forward to future reviews.

    "Ideally, it would be interesting to see a 720p mode on 1440p screens as it would offer perfect scaling, with one logical pixel being mapped to exactly four physical ones, without the need for interpolation and upscaling artifacts"

    If Samsung ever decides to put a 1440p panel on the GS6, I seriously hope they allow a 720p mode in their power saving options. Even if pentile, It would be MUCH sharper than any other 720p AMOLED panel since it's up-scaled. Actually, I seriously interested to see how it would look like. Plus, the added performance and battery life would be legendary on a phone faster and more efficient than the current GS5. Totally intriguing.
  • lilmoe - Saturday, September 13, 2014 - link

    Oh, this is just a suggestion. If you must use browser benchmarks to measure platform performance (sighs...), wouldn't it be better to use the stock browser since it's what most people use? You know, since the stock browser is usually more optimized for that specific device and generally performs better than Chrome. Using Chrome to see the difference of Android devices in comparison is OK since they'd be using the same browser running on the same OS, but definitely NOT OK in comparison with other platforms.

    Please correct me if I'm wrong, because I'm positive that I'm not.
  • aryonoco - Sunday, September 14, 2014 - link

    Thanks for the great review, this was the first time that any publication has exposed the inner workings of a Hisilicon SoC, and you've done a great job of that. However I wanted to mention here that I strongly disagree with your analysis of the software.

    Designing software that's going to be used by mass users is a constant balancing act between exposing enough power to satisfy different user requirements and power users, and yet keeping the UI simple enough so that the vast majority of users are not overwhelmed by the array of features. The Permission Management feature here, similar to those baked into many custom ROMs goes well over the line and is a huge user experience disaster. To ship an OEM ROM with this, is begging for a deluge of support calls from clueless customers who have disabled things and then wonder why their phone doesn't work as intended.

    I'm not saying that the current permission management scenario in Android is perfect, far from it. I don't think anyone has figured out the perfect balance of how to inform users about third party apps without scaring them, turning the notices meaningless, or overwhelming users.

    One of Anand's greatest assets was his ability to articulate his vision of good UI in various products. Him and Brian could explain why certain choices were made (for example in terms of treatment of external storage on Android, or the design tradeoffs about non-replaceable batteries) and the guiding principles behind them. File managers are archaic and confusing to 90% of users. I know the tech-savvy AT readership will disagree, but the whole concept of files and directories are broken for average users, especially on a device like a phone, and they are better off being abstracted away from them. Your comments on file managers in KitKat, or your praise of Huawei's software "enhancements" shows a lack of understanding of where the line is when it comes to UX design.

    I hope that now that Anand is gone, AT doesn't become a place where the writers are blind to the needs of average customers. We do not need Android to regress to the wild days of Gingerbread, or worse, Windows Mobile.
  • Ethos Evoss - Sunday, September 14, 2014 - link

    Well, you complaining about huawei logo or writing missing and main thing is that you NEVER complained on iphones that they NEVER put writing on their phones but that is alright ? h ? people are so pathetic .. if apple wud make soome plastic dick sticking out from phone you guys would say that is fine bcos it is iphone and we will forgive that we will get used to it .. oohh jeezz naive people
  • akshayprbhu - Friday, October 10, 2014 - link

    the writings are a part of the mandatory regulations to denote the compliance with the telecom regulations. and it does not eat up too much space on the back.
  • darkich - Sunday, September 14, 2014 - link

    Absolutely great analysis. Andrei and Joshua, keep these top notch write ups coming!
  • SeleniumGlow - Monday, September 15, 2014 - link

    I was hoping that the Kirin processor would have a comparison with the MediaTek MT6592. But I guess there are some obvious differences in the Big Little implementation that will prevent it from being a good comparison.
  • siberstorm - Monday, September 15, 2014 - link

    The mediocre camera and obvious cutrate shoddiness (wtf the stabilization is just the 1080p field cut down to 720p with none of the rest of the sensor used, so ghetto) is unacceptable and this goes for the mate 7 as well. So bye bye huawei. I am still interested in the lenovo vibe z2 pro aka k920 and would love a review of that phone, but the chances of lenovo sending one to anandtech are slim, considering they arent gunning for the global market like huawei is.

Log in

Don't have an account? Sign up now