System Performance

The Nexus 5X sits in an interesting position as far as its price goes. I don't know many other devices that are priced at the high end of the $300 range, as usually an OEM targets between $250-300 or somewhere around $450. This gives Google some room to play around with what hardware they offer, as the Nexus 5X is not competing directly with flagship devices like the Nexus 6P is. On the other hand, the 5X probably doesn't bring in a ton of profit for Google or LG due to its margins, and it seems more like a vessel for bringing Android to a wider base of customers by offering something good at a lower price than one might expect.

While the Nexus 6P uses Qualcomm's Snapdragon 810 SoC in order to be competitive with other flagships from a specs and marketing standpoint, the Nexus 5X takes a step down to Snapdragon 808. This is a 6 CPU core part, with a quad core Cortex-A53 cluster that runs at up to 1.4GHz, and a dual core Cortex-A57 cluster that peaks at 1.8GHz. This is the same SoC used in the LG G4, and so in tests that are more software independent we should see similar performance to the G4. Otherwise tests that are more influenced by software like PCMark may see improvements or reductions in performance depending on the situation, as the Nexus 5X ships with Android Marshmallow, while the G4 shipped with Lollipop.

Kraken 1.1 (Chrome/Safari/IE)

Google Octane v2  (Chrome/Safari/IE)

WebXPRT 2015 (Chrome/Safari/IE)

JavaScript performance on the Nexus 5X is different than the G4 in some interesting ways. Kraken ends up being around 700ms slower on average, and I've run the test several times to confirm this. Octane actually gives the lead to the 5X, as does WebXPRT 2015, with the gap between the two phones in the latter test being very significant. This is likely the result of improvements to Chrome in the time between the G4 review and now, and I'm not too sure what's causing the performance gap in Kraken.

Basemark OS II 2.0 - System

Basemark OS II 2.0 - Memory

Basemark OS II 2.0 - Graphics

Basemark OS II 2.0 - Web

Basemark OS II 2.0 - Overall

BaseMark pegs the Nexus 5X's overall performance as being in the middle of our sample of results. I've never been very fond of simply averaging test results, but when examining the specific sub scores we can see that the Nexus 5X does surprisingly well in the NAND memory portion of the test, while most of the other scores actually do fall in the middle of the charts, and so in this case the overall result is actually fairly accurate. Later in the review you'll see that this storage result is somewhat suspect, and I would speculate that the reason it's noticeably higher than the G4 is software optimizations made in Android Marshmallow rather than a faster NAND solution.

PCMark - Web Browsing

PCMark - Video Playback

PCMark - Writing

PCMark - Photo Editing

PCMark - Work Performance Overall

In PCMark's overall score we see that the Nexus 5X is actually at the very bottom of the chart. However, as usual it's important to analyze each sub score to see exactly what is contributing to the overall score. In this case it's clear that the writing sub test is what kills the score for 5X, while the rest of the results are closer to the median score of all our comparison devices. The big question is why the 5X does so poorly in the photo editing test. PCMark can be heavily influenced by software changes, and to me it seems that some change in Android Marshmallow's EditText view has caused regressed performance compared to Lollipop. I observed a large decrease in performance when I re-ran the test on the Nexus 6 to confirm this. At the same time, the web browsing and photo editing scores on Marshmallow are clearly much higher than on Lollipop, and so I think in most cases you would actually observe better performance on the Nexus 5X than the LG G4, rather than the substantially worse performance that the overall score implies.

Sustained Performance

I think it's very important to clarify that some of the benchmarks we use typically only run for a fairly short period of time. Kraken and Octane can be completed in well under one minute, while WebXPRT 2015 actually runs for ten minutes. BaseMark OS II and PCMark also take a few minutes to run, but it's definitely not the same workload length as what you'd see while playing a game or editing a video. Because the Nexus 5X uses Snapdragon 808 I wanted to take a look at what happens to the CPU when there's a heavy load placed on it for a prolonged period of time. I also wanted to compare the results to those from the Nexus 5 and Nexus 6, to see how the devices compare once their CPU has throttled to a more realistic clock speed for the real world than the peak performance which typical benchmark results will show.

To see how the CPU behaved during a heavy workload I profiled clock speeds for all the CPU cores while running BaseMark OS II's battery test. This was done on the Nexus 5, Nexus 6, and Nexus 5X. Because the frequencies of the cores oscillate heavily I've graphed the results using longer intervals between points than what is possible to poll, as what I really wanted to show was the behavior of the CPU over time which isn't visible with the noise that plotting every millisecond creates.

Stripping out data points creates some visual errors, as it makes it appear that an SoC spends longer dropped to a low frequency between peaks than it actually did. The key points to get from the graphs above are that for some reason the Snapdragon 800 SoC in the Nexus 5 only ends up using 3 of its 4 cores most of the time, with the frequency on the other three Krait 400 cores oscillating between 1GHz and 1.6GHz. The Snapdragon 805 in the Nexus 6 keeps all four cores at their max frequency for about twelve minutes before they all throttle down to 2GHz and remain there for nearly two hours. Meanwhile, Snapdragon 808 can only keep its two A57 cores at their peak frequency for two minutes before throttling both down to 633MHz and putting the A53s up to their peak 1.44GHz. After twelve minutes the A57s are just shut off entirely, and you're left with a cluster of 4 A53 cores at 1.44GHz. I didn't bother running this test as long as I did for Snapdragon 800 and 805 because the events at the two and twelve minute marks tell you everything you need to know.

Of course, the performance of a device can't be determined simply by the number of cores and the clock speed. The most relevant comparison for the Nexus 5X is the Nexus 5. Krait 400 does have an IPC lead over Cortex-A53, particularly in workloads where out-of-order execution can be leveraged. However, with the Nexus 5 we're looking at three Krait 400 cores hovering between 1 and 1.6GHz, while the 5X can assign threads to four 1.44GHz Cortex A53 cores and two 633MHz A57s for the first twelve minutes. Past this point I think which device performs better is going to depend on the actual workload, and if you're running a CPU-intensive app that isn't heavily parallelized the Nexus 5 may very well end up being faster. For more parallel workloads, or tasks that only require short bursts of performance that are more friendly to the Cortex-A57 cores, you'll see the Nexus 5X providing better performance.

I actually would have liked to have a Snapdragon 801 data point, but Snapdragon 805 in the Nexus 6 is also a relevant comparison considering it was the only Nexus smartphone from last year. In this case I think it's pretty clear that any sustained workload lasting longer than 2 minutes is going to be substantially faster on a Snapdragon 805 device, and truthfully if your workload takes advantage of multiple cores it's likely that Snapdragon 805 will always be faster even within those first two minutes where Snapdragon 808's A57s are at their peak frequencies. I wouldn't want to say anything for certain, but this is probably true for Snapdragon 801 as well.

It's disappointing that this year's Qualcomm silicon means that the performance improvement over a two year old Nexus 5 is not very large. Our past published data shows that the behavior of the Snapdragon 810 SoC in the Nexus 6P will almost certainly behave in the same manner, and in that case you'll actually be looking at an overall regression compared to the Nexus 6 when your workload spans any longer than a minute or two.

On the one hand, I think it would have been better for Google to wait until Snapdragon 820 launched so it could be utilized. On the other hand, that would involve pushing back devices that were obviously in development for some time in collaboration with two major hardware partners. It's not clear if waiting would have made any difference for the Nexus 5X anyway, as it needs to meet a lower price than the Nexus 6P and so there's less room to spend on a more expensive FinFET SoC.

I personally haven't been pushing the 5X very hard, as I still haven't built up a good library of games on Android yet, and I've been leveraging Google Photos to move images and videos from the device to my computers instead of editing them on-device. While the most basic interactions like navigating the UI and scrolling seem to perform well, you're not going to see the performance that you would expect based on the SoC's specs when editing videos or photos that you've recorded on the device, or other similarly CPU intensive tasks. I can certainly forgive the issue when the device costs $379, but I don't think it would be as easy to pass if it's also true of the 6P, and overall I'm most disappointed about the relative lack of improvement over the original Nexus 5 despite the two year gap between the two.

Display System Performance Cont'd: GPU and NAND
POST A COMMENT

197 Comments

View All Comments

  • zeeBomb - Monday, November 9, 2015 - link

    Well well well! What do we have here? A 5x review without the 6P? I'll take it. Reply
  • Der2 - Monday, November 9, 2015 - link

    Okay, read the whole review. Great work as always Brandon, and I just wanna put my thoughts out:

    That sustained performance though! Two minutes... Eek! Although that hits me right to my kokoro I think it isnt much of a big problem as someone like me who browses waaay more than gaming.

    NAND performance. Oh man. One day AES hardware will be noticed. Or maybe a case of f2fs storage might help...hmm.

    Its a blessing that Google is using great camera hardware for the first time. HDR+ All day every day kinda sucks as you basically have to rely on ISP and heavy processing, but as long as I get good photos out of it, I'm okay with that.

    All in all, this is a great device for it's price point. Priced competitively and has good improvements over the original 5. It really comes down to how google can maintain such good outcomings of a phone for a lot cheaper than other OEMS...

    And I will always respect them for doing so.
    Reply
  • zeeBomb - Monday, November 9, 2015 - link

    Wow, great stuff you mentioned there man (totally something I would say!) As google has some losses in this device, the GOOD does outweigh the BAD in this type of scenario, which I applaud google for. F2FS may be still young, but the innovation to multiply your read write speed is something I can wonder a lot of phones will benefit from.

    The 808 may be a bummer for some, but a wiser choice to implement without sacrifing so much performance, as it really comes down to Qualcomm to learn from their mistakes and hopefully not make a crucial mistake like this again.

    BTW the camera...woot! Can walk around and snap pics like no tomorrow! (P.S: The 5X doesn't have EIS, but only the 6P does).
    Reply
  • Billie Boyd - Friday, November 27, 2015 - link

    Between 5x and N6. I recommend going for N6 instead. Its highly rated by the consumers based on satisfaction (see http://www.consumerrunner.com/top-10-best-headphon... for instance...) Reply
  • Kookas - Friday, December 18, 2015 - link

    It's also huge, however. It's nice to keep devices that you have to carry about all day compact. Reply
  • coolhardware - Monday, November 9, 2015 - link

    Enjoyed this one! Definitely more likely to look at picking up a 5X after reading the Anandtech review.

    Interesting to see where the Nexus 5X slots in with other Nexus devices, specifically when it comes to pixel density (PPI)
    http://pixensity.com/search/?search=nexus
    Reply
  • Kumar Anand - Tuesday, November 10, 2015 - link

    I am running Wi-Fi throughput test on Nexus 5X using iperf and I am getting much higher numbers than anandtech. Here is information regarding my test bed -

    a) iperf version : 2.0.5
    b) iperf command used:
    iperf -s -w 512k -i1 -u
    iperf -c <ip> -w 512k -i1 -t 300 -u -b 300M -P3
    c) AP: Netgear R8000, VHT80, CH:157, Open Security.
    d) Environment: OTA (over the air) in a clean environment (i.e. no interference from other clients)
    e) 2 runs each for UDP DL/UL, each iperf run is for 5min (300s).
    f ) 3 iperf parallel streams (iperf -P3 option)

    RESULTS:
    UDP Uplink (UL): 642 Mbps, 702 Mbps
    UDP Downlink (DL)): 678 Mbps ,708 Mbps

    anandtech - Could you please clarify regarding your tests? I am curious to understand why your numbers are not matching my peak numbers.

    1) What is SW build loaded on your Nexus 5X?
    2) What is the AP configuration and make and model?
    3) What is the tool/command being used?
    Reply
  • jay401 - Tuesday, November 10, 2015 - link

    Does this phone have WiFi Calling? Reply
  • DLimmer - Thursday, November 12, 2015 - link

    Yes and no. A quick summary of Google-Fi in this review would help answer this question.

    Yes: Google-Fi is Google's solution to phone plans/service. It replaces your current carrier at a pre-paid rate ($20 for unlimited U.S. text and voice, $10 per 1GB of data... only pay for the data you use). Google has sourced cellular service from 2 companies and many Wi-Fi hot spots, and has placed hardware in the 6, 6P and 5X to enable seamless usage and switching.

    No: Wi-Fi calling is only available on the Google-Fi network.

    As stated, only 3 phones currently possess the hardware to use Google-Fi.
    Reply
  • Der2 - Monday, November 9, 2015 - link

    In my opinion, this is Googles finest phone yet: where the fan has schoice to decide! Reply

Log in

Don't have an account? Sign up now