System & CPU Performance

The Nexus 6P comes with a Snapdragon 810 designed by Qualcomm. This is a big.LITTLE 4x A53 @ 1.55GHz + 4x A57 @ 1.95GHz SoC. As we’ve hopefully come to be very familiar with the chipset over the last couple of months, the key characteristics with which the 6P can differentiate itself from other Snapdragon 810 devices is through software optimizations. In particular the fact that the Nexus 6P comes with Android 6.0 Marshmallow should allow it to be able to showcase some improvements which we’ll dive into a bit later.

First we start by comparing performance of some of our browser-based benchmarks. These are predominantly Javascript tests which require large single-core performance out of the device’s SoCs.

Kraken 1.1 (Chrome/Safari/IE)

In Kraken the Nexus 6P is able to showcase a very good score that’s only beat by, oddly enough, the LG G4. As we’ve come to discover over the past year OEM browser libraries play a large role in device performance, even though we’re using the same Chrome build across different devices we see large differences in performance even within devices who employ the same SoC. It’s relatively unnerving to see this fragmentation in the ecosystem and in particular Chrome performing so differently across devices.

Google Octane v2  (Chrome/Safari/IE)

In Octane the Nexus 6P again performs very well, this time again beating our other devices such as the HTC One M9 or the Xiaomi Mi Note Pro. Among Android devices, only the Galaxy Note 5 - which on Octane is able to show equal performance as it does in its optimized stock browser - is able to beat it.

WebXPRT 2015 (Chrome/Safari/IE)

On WebXPRT again we see the 6P performs extremely well among Android devices, only being able to be beat by Samsung’s Exynos 7420 devices in the stock browser.

Continuing onto our system benchmarks, we start with Basemark OS II 2.0 from Basemark (formerly Rightware).

Basemark OS II 2.0 - Web

In the web test the Nexus 6P is yet again found at the high-end of the charts as it is able to provide good numbers. As we’ve seen in reviews such as on the Mate S it’s not necessarily raw performance that is demanded in these tests but also performance latency which plays a big role.

Basemark OS II 2.0 - Graphics

The graphics sub-test of Basemark has always been kind to the Adreno GPU so here again we see the Nexus 6P perform well, although not quite up to par with the other Snapdragon 810 devices we’ve tested in the past.

Basemark OS II 2.0 - Memory

The Nexus 6P comes in a surprising first place on Basemark OS’s memory test. Again this is a mainly NAND-limited test but in contrast to our other synthetic test, performance and access patterns try to simulate more real-world applications.

Basemark OS II 2.0 - System

While the other tests try to test more realistic workloads, the system benchmark is all about measuring peak performance in a given set of scenarios. Here the Nexus 6P fares similarly to the Xiaomi Mi Note Pro but falls behind Exynos 7420 devices such as the Note 5.

Basemark OS II 2.0 - Overall

While I’m not a great fan of overall aggregate benchmark scores, we still see the Nexus 6P among the top of today’s currently available Android devices.

Moving on to PCMark from Futuremark, we’ll use a suite of tests that not only try to mimic real-world usage patterns, but actually make use of APIs that we currently find in use by many day-to-day applications.

Starting with the web browsing test we find the application use Android’s built-in WebView container which relies on OS-dependent components.

PCMark - Web Browsing

Here we see the Nexus 6P lead performance, slightly beating the Note 5. We’re also likely seeing advantages due to Android 6.0 as the Mi Note Pro, our other device with the Snapdragon 810 lags over a thousand points behind.

PCMark - Video Playback

On the video playback score the Nexus 6P comes in towards the middle of the pack. The video test is a benchmark of both the video decoding hardware and software layers of the device, as well as the NAND speed, as fast seeking through the video is performed to test out how rapidly the device can resume playback.

PCMark - Writing

Now onto the writing test we come to one of the larger mysteries of the new Nexus 6’s performance. Both the Nexus 5X and the 6P seem to have large issues with PCMark’s writing test. The test itself consist of text manipulation and some file I/O, but most importantly it’s that this is purely a Java based test. Due to the way Android is architected, this means the code is handled and executed by the Android RunTime (ART). Futuremark have done a fantastic job in creating a test-case which is very sensitive to performance differences in the runtime.

At first when seeing these scores I thought that this was a side-effect of Android 6.0’s new big.LITTLE optimizations (which we’ll get back to in a later section), but even after turning those settings off the scores remained the same. After testing some other Java-based benchmarks I came to the conclusion that this has to be a software issue.

PCMark - Photo Editing

The photo editing uses RenderScript kernels to apply image processing on a set of pictures. With help of a powerful GPU the Nexus 6P performs top of the class

PCMark - Work Performance Overall

Due to the disappointing writing sub-score the Nexus 6P ends up third in the overall PCMark work performance score. Nevertheless, this is a good showing for the Snapdragon 810 device as it manages to slightly beat the Mi Note Pro and the HTC One M9.

Software UI, NAND & WiFi Performance GPU Performance & Device Thermals


View All Comments

  • tuxRoller - Monday, December 21, 2015 - link

    Do you have a reference for saying that they don't make use of idle loops and dvfs?
    If that's the case, and I don't think it is, then what apple has done is even more amazing: the highest performing soc available is capable of being run FLATOUT for half a day on their tiny batteries. If they made use of even minimal power saving a9 devices would last for DAYS.
  • tipoo - Tuesday, December 22, 2015 - link

    I think they probably meant the GFXbench battery run test and final run FPS test, every other SoC throttles down by the last one, where A9 keeps a high speed but kills the battery sooner.

    I think that speaks more to the throttling issues of other SoCs, even if it accidentally raises gaming battery life.
  • tipoo - Tuesday, December 22, 2015 - link

    "anyone who knows hardware knows single threaded architectures will score higher"

    So explain, please. And neither iOS nor A9 are single threaded, all SoCs since the A5 with the exception of the A8X are dual cores, A8X being tri-core. iOS scales to threads just fine as shown with the third core being used just fine in the A8X. Apple just chose higher per-core performance, since it's more usable than the same performance spread across 8 cores.
  • NEDM64 - Monday, December 28, 2015 - link

    "Android was built to be a true multi-tasking OS...Apple was not..."

    Fanboy tears?

    "Apple" OS's, based on their open-source project, Darwin, are microkernel-based, non-peremptitive multitasking operating systems.

    Just like OS X, iOS is a truly multitasking OS.

    And if you want to cry even more, then explain why the Pixel C doesn't offer side-by-side multitasking and iPads with iOS 9 do?
  • usman_raza - Wednesday, December 16, 2015 - link

    2nd Comment :)
  • Anustart - Wednesday, December 16, 2015 - link

    Loser Reply
  • AL KASR - Wednesday, December 16, 2015 - link

    thanks, but what about random read and random write for the nand, which is the most important! Reply
  • Andrei Frumusanu - Wednesday, December 16, 2015 - link

    I had to leave them out due to an issue with the 3.6 version of the benchmark not being able to complete those sub tests, we'll be investigating the matter and in the future we'll also migrate to AndroBench 4.0.

    Here's the 4.0 scores for the device:

    Encrypted: 75.7MB/s seq read, 40.6MB/s seq write, 7.4MB/s rand read, 1.0MB/s rand write.
    Unencrypted: 179.7MB/s seq read, 52MB/s seq write, 14.73MB/s rand read, 6.3MB/s rand write.
  • Olaf van der Spek - Wednesday, December 16, 2015 - link

    Why do the random scores take such a hit from encryption? The SoC should be fast enough to encrypt 6.3MB/s so I can't think of a reason for rand write to drop to 1.0MB/s.. Reply
  • Andrei Frumusanu - Wednesday, December 16, 2015 - link

    The random test uses 4KB segments and it's likely that due to that there's a lot of system overhead when making such short I/O operations. Reply

Log in

Don't have an account? Sign up now