GPU Performance

On the GPU side, HiSilicon continues to rely on what is by now a quite old IP in the form of the ARM Mali T628. This is the same MP4 GPU configuration found in the Hi3630 (Krins 920's) of last year, and saw little change other than a small 80MHz boost in clocks to 680MHz. The Honor 6 and Mate 7 already disappointed in GPU performance, and we're not expecting the P8 to have any large gains over those predecessors.

We start off with 3DMark 1.2 Unlimited, which has both a graphics heavy test as well as a combined GPU and CPU heavy test.

3DMark 1.2 Unlimited - Graphics

3DMark 1.2 Unlimited - Physics

3DMark 1.2 Unlimited - Overall

The P8 performs as expected, as it struggles to keep up with the competition. Interestingly, it performs worse than the Kirin 920 even though it's clocked higher than its counter-part, pointing out that the weaker CPU actually might be limiting the graphics performance.

GFXBench 3.0 Manhattan (Onscreen)

GFXBench 3.0 T-Rex HD (Onscreen)

GFXBench 3.0 Manhattan (Offscreen)

GFXBench 3.0 T-Rex HD (Offscreen)

GFXBench is a more CPU-light benchmark and we see the P8 correctly outperform the Honor 6 & Mate 7 as one would expect it to. Again, we see very bad performance for a 2015 flagship as the P8 still can't match up to devices released 18 months ago.

BaseMark X 1.1 - Dunes (High Quality, Onscreen)

BaseMark X 1.1 - Hangar (High Quality, Onscreen)

BaseMark X 1.1 - Dunes (High Quality, Offscreen)

BaseMark X 1.1 - Hangar (High Quality, Offscreen)

BaseMark X paints a similar picture as GFXBench. There's not much we can say to make the scores seem better for the P8, as the GPU remains very underwhelming.

GPU Power

While I mentioned in the introduction that I wasn't able to properly dismantle the P8 without damaging it, I did try to get some numbers through the internal fuel-gauge. While these numbers are definitely not as precise as measuring directly on the hardware and should be taken with a grain of salt, they nevertheless give us a good reference point and estimate on how the SoC fares.

The P8 seems to consume around 3.7W of load power in the T-Rex Offscreen test. As a reminder, under the load power metric we understand the resulting difference of the total power of the device subtracted by the average power the device consumes in its idle state. This is done to be able to compensate for the various screen sizes and their efficiency, and to cancel out power other eventual passive platform components.

3.7W is still sadly too high from what a smartphone SoC should be allowed to dissipate in normal conditions and will lead to unavoidable thermal throttling as we see in the battery rundown log:

GFXBench 3.0 Performance Degradation

The P8 doesn't even manage to keep its top frequency for more than a single run, and after 7 minutes it settles down and between 50% and 40% of maximum frequency. The end performance degradation value comes in at 8.71fps, a result ironically beat only by last year's Ascend P7's and the Kirin 910T.

T-Rex Offscreen Power Efficiency (Load Power)
  Mfc.
Process
FPS Avg. Power Perf/W
Exynos 7420 (S6) 14LPE 56.3 4.82W 11.63 fps/W
MT6595 (MX4) 28HPM 23.3 2.42W 9.55 fps/W
Exynos 5430 (MX4Pro) 20LPE 28.7 3.55W 8.08 fps/W
Exynos 5433 (Note 4) 20LPE 37.3 5.35W 6.97 fps/W
Exynos 5430 (Alpha) 20LPE 31.3 4.88W 6.41 fps/W
Kirin 930 (P8 Estimated) 28HPM 17.0 3.69W 4.60 fps/W

When looking at SoC power efficiency under 3D load that we've tested over the last few months we see that the Kirin 930 ends up in quite a dire situation as it gets beat by all other SoCs we currently have data on.

HiSilicon needs to invest in more silicon area and adopt higher GPU core numbers to be able to run at lower frequencies and lower voltages if it wants to stay competitive in graphics performance. It's weird to see the stark contrast of HiSilicon's current 28nm 4-core silicon versus Samsung's 14nm 8-core in the Galaxy S6, with both devices coming out in the same time-frame and both of them essentially employing the same GPU IP family.

It will be interesting to see how Huawei can take advantage of the next generation manufacturing processes as future Kirin SoCs are expected to be made in TSMC's 16nm FinFET node.

CPU & System Performance WiFi, GNS and NAND Performance
Comments Locked

104 Comments

View All Comments

  • Andrei Frumusanu - Saturday, June 13, 2015 - link

    Because our other editors are able to collect the objective data?
  • Ethos Evoss - Saturday, June 13, 2015 - link

    objective data these days are completely out of scale total lies .. and 95% incorrect ..
  • alin - Thursday, June 4, 2015 - link

    All manufacturers should have an option to revert the software to a vanilla alternative.
    They can supply it on their website as an option to every user/buyer of their devices.
    Many custom rom's just ruin the hole phone experience. The hardware is great but the software is crap...
  • Ethos Evoss - Friday, June 12, 2015 - link

    the main problem is shitty android and it's core so shitty linux
    Huawei said they going to start making their OWN OS which will be implemented into their mobiles in future!
  • jjj - Thursday, June 4, 2015 - link

    Any chance you'll get a SD810 and 808 soon to test GPU power? And if you do can you also monitor CPU clocks under that load? I don't even dare to imagine how hard the CPU must throttle when the GPU is loaded.
  • Ethos Evoss - Friday, June 12, 2015 - link

    pleease u don't know that already SHIT-DRAGON 810 is EPIC FAIL of the year?? wake up from your dreaam man !
  • Novacius - Thursday, June 4, 2015 - link

    Is the memory controller 2x16 bit or 2x32 bit?
  • Novacius - Thursday, June 4, 2015 - link

    Because the article says "dual channel 32 bit".
  • Kepe - Thursday, June 4, 2015 - link

    Dual channel 32-bit = Two 32-bit memory channels. Plus, a 16-bit memory controller could only address 64KB of memory, compared to the maximum of 4GB for a 32-bit controller... Having 128KB of RAM in a smartphone wouldn't be very wise. It could probably boot in to something like DOS, but Android would definitely not work.
  • Pissedoffyouth - Friday, June 5, 2015 - link

    Your confusing bus length with address space.

Log in

Don't have an account? Sign up now