Kirin 980 Second Generation NPU - NNAPI Tested

We’ve tested the first generation Kirin NPU back in January in our Kirin 970 review – Back then, we were quite limited in terms of benchmarking tests we were able to run, and I mostly relied on Master Lu’s AI test. This is still around, and we’ve also used it in performance testing Apple’s new A12 neural engine. Unfortunately or the Mate 20’s, the benchmark isn’t compatible yet as it seemingly doesn’t use HiSilicon’s HiAI API on the phones, and falls back to a CPU implementation for processing.

Google had finalised the NNAPI back in Android 8.1, and how most of the time these things go, we first need an API to come out before we can see applications be able to make use of exotic new features such as dedicated neural inferencing engines.

“AI-Benchmark” is a new tool developed by Andrey Ignatov from the Computer Vision Lab at ETH Zürich in Switzerland. The new benchmark application, is as far as I’m aware, one of the first to make extensive use of Android’s new NNAPI, rather than relying on each SoC vendor’s own SDK tools and APIs. This is an important distinction to AIMark, as AI-Benchmark should be better able to accurately represent the resulting NN performance as expected from an application which uses the NNAPI.

Andrey extensive documents the workloads such as the NN models used as well as what their function is, and has also published a paper on his methods and findings.

One thing to keep in mind, is that the NNAPI isn’t just some universal translation layer that is able to magically run a neural network model on an NPU, but the API as well as the SoC vendor’s underlying driver must be able to support the exposed functions and be able to run this on the IP block. The distinction here lies between models which use features that are to date not yet supported by the NNAPI, and thus have to fall back to a CPU implementation, and models which can be hardware accelerated and operate on quantized INT8 or FP16 data. There’s also models relying on FP32 data, and here again depending on the underlying driver this can be either run on the CPU or for example on the GPU.

For the time being, I’m withholding from using the app’s scores and will simply rely on individual comparisons between each test’s inference time. Another presentational difference is that we’ll go through the test results based on the targeted model acceleration type.

AIBenchmark - 1a - The Life - CPU AIBenchmark - 6 - Ms.Universe - CPUAIBenchmark - 7 - Berlin Driving - CPU

The first three CPU tests rely on models which have functions that are not yet supported by the NNAPI. Here what matters for the performance is just the CPU performance as well as the performance response time. The latter I mention, because the workload is transactional in its nature and we are just testing a single image inference. This means that mechanisms such as DVFS and scheduler responsiveness can have a huge impact on the results. This is best demonstrated by the fact that my custom kernel of the Exynos 9810 in the Galaxy S9 performs significantly better than the stock kernel of the same chip of the Note9 in the same above results.

Still, comparing the Huawei P20 Pro (most up to date software stack with Kirin 970) to the new Mate 20, we see some really impressive results of the latter. This both showcases the performance of the A76 cores, as well as possibly improvements in HiSilicon’s DVFS/scheduler.

AIBenchmark - 1c - The Life - INT8AIBenchmark - 3 - Pioneers - INT8AIBenchmark - 5 - Cartoons - INT8

Moving onto the next set of tests, these are based on 8-bit integer quantized NN models. Unfortunately for the Huawei phones, HiSilicons NNAPI drivers still doesn’t seem to expose acceleration to the hardware. Andrey had shared with me that in communications with Huawei, is that they plan to rectify this in a future version of the driver.

Effectively, these tests also don’t use the NPU on the Kirins, and it’s again a showcase of the CPU performance.

On the Qualcomm devices, we see the OnePlus 6 and Pixel 3 far ahead in performance, even compared to the same chipset Galaxy S9+. The reason for this is that both of these phones are running a new updated NNAPI driver from Qualcomm which came along with the Android 9/P BSP update. Here acceleration if facilitated through the HVX DSPs.

AIBenchmark - 1b - The Life - FP16AIBenchmark - 2 - Zoo - FP16AIBenchmark - 4 - Masterpiece - FP16

Moving on to the FP16 tests, here we finally see the Huawei devices make use of the NPU, and post some leading scores both on the old and new generation SoCs. Here the Kirin 980’s >2x NPU improvement finally materialises, with the Mate 20 showcasing a big lead.

I’m not sure if the other devices are running the workloads on the CPU or on the GPU, and the OnePlus 6 seems to suffer from some very odd regression in its NNAPI drivers that makes it perform an order of magnitude worse than other platforms.

AIBenchmark - 8 - Berlin Driving - FP32

Finally on the last FP32 model test, most phones should be running the workload on the CPU again. There’s a more limited improvement on the part of the Mate 20.

Overall, AI-Benchmark was at least able to validate some of Huawei’s NPU performance claims, even though that the real conclusion we should be drawing from these results is that most devices with NNAPI drivers are currently just inherently immature and still very limited in their functionality, which sadly enough again is a sad contrast compared where Apple’s CoreML ecosystem is at today.

I refer back to my conclusion from early in the year regarding the Kirin 970: I still don’t see the NPU as something that obviously beneficial to users, simply because we just don’t have the software applications available to make use of the hardware. I’m not sure to what extent Huawei uses the NPU for camera processing, but other than such first-party use-cases, NPUs currently still seems something mostly inconsequential to device experience

First Cortex-A76 SoC - SPEC2006 Performance & Efficiency System Performance
Comments Locked

141 Comments

View All Comments

  • cha0z_ - Tuesday, November 20, 2018 - link

    I don't like how the best phone samsung made this year is not here (the note 9). That phone has a lot bigger body vs s9 and 3 times bigger heatpipe that is also better (the body of the phone heats, but the SOC is not throttled. Actually note 9 in heavy use is hotter than the s9+ but sustains better ;) ) + it's tweaked not for peak performance, but sustained performance + samsung DID improve the kernel and the control of the exynos 9810. I am sure all the factors will lead to noticeable difference compared to the s9 exynos tests from the start of the year.

    I know that you are tired of the exynos 9810, we all know that chip is far worse than the rivals, but still it would be better to show it in it's best light instead of the all negativity. Comparing in a single table a phone twitce smaller than the other and drawing conclusions about the SOCs inside is plain wrong.
  • eastcoast_pete - Tuesday, November 20, 2018 - link

    @Andrei:Any statement from Huawei on how long they will continue to provide OS updates for, and how quickly after Google releases them? With prices approaching 1000 dollars/euros/pounds, the old "release and abandon" would be a bit too much. Thanks!
  • abufrejoval - Tuesday, November 20, 2018 - link

    It doesn't get any better: Here you have all the hardware to turn into a credible workstation with sufficient compute, gaming and even inference power to do 90% of what normal PC users would need with UPS, storage and a high resolution touch screen included at pocket size and laptop budgets....

    But you simply cannot get the power onto a screen large enough to work with all day (Miracast is really doesn't have acceptable fidelity)

    And they simply won't let you take control over what could be a very personal and very portable workstation, because they deny you control over the computer you purchased (no rooting).

    All that power in a form factor that precludes putting it to work just drives me knocking my head into the wall!
  • whyamihere - Thursday, November 22, 2018 - link

    If possible do you think you could look at the power consumption of a BOE screen on the Mate 20 pro. I'm wondering if the battery issues you saw on the pro model had to do with the LG screen, as LG screens on the pro model seem to have issues such as really bad green tint that gets worse over time.
  • Jalk44 - Thursday, November 22, 2018 - link

    A: it's not the first QHD phone by Huawei,that's was the mate 9 pro

    B: it's also not the first phone with both front and back full curved glass, that would be the mate rs
  • MyFluxi - Thursday, November 22, 2018 - link

    hey, can you do a screen battery test with the BOE screen and also a general review on the boe screen. some saying that the vibrancy is less on the BOE but the uniformity is better
  • ballsystemlord - Friday, November 23, 2018 - link

    Hi. Your local S+G corrector here. Todays mistake is an obvious one, the word "if" should be substituted by the word "is".
    "Here acceleration if facilitated through the HVX DSPs."
    --
    "Here acceleration is facilitated through the HVX DSPs."
    I lightly read the last 3 pages. I got tired of reading everything.
  • salbashi - Tuesday, November 27, 2018 - link

    Did Anandtech notice any benchmark mode on Mate 20 or Mate 20 Pro this time around?
    Cause that would be Huawei caught cheating again right after P20 and P20 Pro.
  • Davidsic - Wednesday, November 28, 2018 - link

    Hello, my first Mate 20 Pro had the same brightness anomaly you are talking about (LG screen) and my second one that i recieved yesterday have the same issue and it's a BOE screen !
  • AlexTi - Sunday, March 17, 2019 - link

    Mate 20 having Qi wireless charging possibility seems to be a mistake in specifications. The one I've just bought definitely lacks it (model number HMA-L29), and specs on Huawei website do not include this feature for non-Pro Mate 20.

Log in

Don't have an account? Sign up now