GPU Performance

CPU performance is one side of an SoC, while GPU performance is the other side. With two years of GPU development between the Nexus 5 and the 5X we're hopefully looking at a substantial uplift in GPU performance. Qualcomm's official figures peg Adreno 418 as 20% faster than Adreno 330 in graphics workloads. To characterize the Nexus 5X's performance during graphics workloads that are similar to those a 3D game would provide I've run it through our standard GPU-focused benchmarks. The first is 3DMark, followed by BaseMark X and GFXBench 3.0.

3DMark 1.2 Unlimited - Graphics

3DMark 1.2 Unlimited - Physics

3DMark 1.2 Unlimited - Overall

The Nexus 5X ends up actually coming in below the Nexus 5 in 3DMark's overall score. This is the result of the much lower score in the physics sub test. However, it's worth noting that the 3DMark physics test has heavy data dependencies and all of our tested devices with bigger out of order cores end up doing poorly. While this is a possible scenario in a real-world program, I wouldn't make too many conclusions from the Nexus 5X's performance here. In the graphics test there's actually a surprising gap between the 5X and the LG G4 which uses the same SoC, and I've been unable to get a score anywhere near it no matter how many times I re-run the test. At least in 3DMark it looks like the LG G4 has a bit of a lead over the Nexus 5X.

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 1.1 - Overall (High Quality)

BaseMark X's results are more in line with what I expected to see from the 5X's GPU. The on-screen results are far ahead of the LG G4, which isn't surprising at all when you consider that the G4 is driving a 2560x1440 panel while the 5X is pushing 1920x1080. Both off-screen results are close enough that they could be ascribed to margin of error, and ultimately BaseMark X shows that there's not really any gap between the absolute performance of the G4 and the 5X, but the 5X will definitely be faster for anything running at native resolution.

GFXBench 3.0 T-Rex HD (Onscreen)

GFXBench 3.0 Manhattan (Onscreen)

GFXBench 3.0 T-Rex HD (Offscreen)

GFXBench 3.0 Manhattan (Offscreen)

The results in GFXBench echo those of BaseMark X. The 5X beats the G4 in both off-screen cases, but only by a small margin. With the 5X being slightly faster than the G4 in both GFXBench and BaseMark X we may be looking at some small driver improvements here, but since all the gaps are so small it may just be coincidence that the 5X is the faster of the two devices in both tests.

Ultimately, both Adreno 418 and 430 are pretty good GPUs, and with the Nexus 5X being priced at $379 I think it offers more than adequate GPU performance for its price. What's interesting is that even though we didn't see Snapdragon 805 show up in many devices, it was in the Nexus 6, and its Adreno 420 GPU is definitely a bit faster than the Adreno 418 in the 5X. The Nexus 6 was also priced much higher than the 5X, and so with the 5X you're definitely getting a lot more GPU performance for your money than you got with the Nexus 6. The performance uplift is definitely greater than Qualcomm's stated 20%, and it's always nice to see something beat expectations.

NAND Performance

When I originally reviewed the Nexus 6 I decided to publish the review without any storage benchmarks, because in my testing I noticed that the results I was getting simply did not add up. Futher investigation revealed that it was the result of the Nexus 6's forced Full disk encryption (FDE), and the encryption and decryption of data being done without the use of high speed, power efficient fixed-function hardware. Later on in the Nexus 9 review Josh noted that there was a significant uplift in NAND performance compared to the Nexus 6, and it was clear that the AES/SHA instructions that are part of the ARMv8 instruction set were helping to reduce the performance impact of FDE.

Since Snapdragon 808 supports the ARMv8 ISA this presents a good opportunity to revisit this topic. The Nexus 5X shares several things with the LG G4, and one of them is its NAND, which is an eMMC 5.0 solution provided by Toshiba with the model number 032G74. While there's not much public information on this storage solution, one would expect that NAND storage speed results from the Nexus 5X closely match those of the LG G4, as if that isn't the case then it's clear that FDE causes a noticeable loss of performance despite ARMv8's cryptographic instructions.

Internal NAND - Random Read

Internal NAND - Random Write

Random read and write speeds both take a hit when compared to the LG G4. While the gaps don't look enormous, the performance with small transaction sizes on mobile devices is hardly great to begin with, and so even these small gaps can matter greatly. In this case both random read and write speeds are both about 30% lower than the G4, which is significant.

Internal NAND - Sequential Read

Internal NAND - Sequential Write

Sequential write speeds on the 5X end up being about equal to the G4, but the gap in sequential read speeds is enormous. Altogether, it's clear that there's still a significant reduction in NAND performance caused by the use of FDE when only using ARMv8's cryptographic instructions to encrypt and decrypt data to be written. This contrasts with comments made by Google engineer David Burke during a Reddit AMA discussing the FDE situation on the Nexus 5X in response to a comment that was referencing the Nexus 6's poor storage performance. What's interesting is that ARM has stated before that the ARMv8 cryptographic instructions are not a substitute for fixed-function hardware, and so it looks like there's a disagreement between ARM and Google on whether or not this is an adequate solution for encryption.

Reduced storage performance is not the only problem with this solution. Waking up the AP to do encryption or decryption every time the disk has to be read from or written to incurs a huge power penalty compared to simply using a hardware AES block and DMA which happens to be what Apple has been doing for about six years now. There are power savings here just waiting for Google to grab them, but they've decided not to do so for a second year now. Google certainly has an interest in getting Android phones to use FDE out of the box in order to combat negative perceptions about Android's security, but I don't think it's acceptable to have such a policy without the necessary hardware to make sure it doesn't affect the device's performance to any significant degree.

The Nexus 5X is certainly in a much better situation than the Nexus 6 was, but Google's FDE policy means you still get significantly reduced storage performance across the board compared to a device with the same NAND. This has various ramifications, ranging from data transfer speeds, to app install times, to performance when apps are updating in the background, to the ability to rapidly take photos and record high bitrate video. I really wish Google would either not ship with forced FDE and allow it to be disabled, or implement the necessary fixed-function AES hardware to avoid the significant performance hit.

System Performance Battery Life, Charging, WiFi
Comments Locked

197 Comments

View All Comments

  • konondrum - Monday, November 9, 2015 - link

    I've had my s6 for about 2 months now, and I've never noticed it getting warm at all.
  • hans_ober - Monday, November 9, 2015 - link

    Btw about charging:

    QC 2.0 uses higher voltages, while USB 2.0 + Power Delivery uses 5V @ higher current.
  • zeeBomb - Monday, November 9, 2015 - link

    So uh...which is better? Which has a lesser chance of catching on fire :p
  • Pissedoffyouth - Monday, November 9, 2015 - link

    voltage. That's why electric fences are like 30,000v and have thin wires. If you have high amperage you get more resistance, so need thicker wires
  • zeeBomb - Monday, November 9, 2015 - link

    Ah. Talk about learning something new everyday! I see. Thanks you two!
  • DanNeely - Monday, November 9, 2015 - link

    USB 3 power delivery offers the best of both worlds. You have 1, 3, and 5Amp options at 5, 12, or 20V. The 12V option is roughly equivalent to earlier quick charge standards and is something that should be relatively easy for desktop PCs to support (since the mobo most runs on 12V anyway); with 20V being intended for laptop chargers; but who knows what will happen over the next few years.

    Qualcom's newest generation of quick chargers support a wide variety of intermediate voltages; with the intent of best tuning the power delivered to what the battery can still take as it approaches full capacity. In the real world I'm not sure how much, if anything, this offers over a conventional high voltage/amperage charger.
  • ciderrules - Monday, November 9, 2015 - link

    Interesting that iPhones have had hardware encryption since way back on the 3GS yet it still hasn't seen adoption by Android device makers, some 6 years later. I'm curious, is there any Android phone with a hardware encryption module? It's not something you see talked about, outside of Anandtech.
  • zeeBomb - Monday, November 9, 2015 - link

    Good question actually...maybe there are a few out there that isn't high end with it.
  • DanNeely - Monday, November 9, 2015 - link

    Doubtful. If Qualcom and Samsung aren't including hardware crypto, I'd be shocked if anyone else is. The various Chinese arm makers are all competing at the end of the market where even a few cents for an extra IP block is a non-trivial concern because it's a significant chunk of their profit margin.
  • tipoo - Monday, November 9, 2015 - link

    Did they have full disk encryption back to the 3GS? For some reason I thought it came with the 64 bit move.

Log in

Don't have an account? Sign up now