System Performance

From an editorial perspective, the SHIELD Android TV may be one of the most frustrating devices we’ve worked on in recent history. Simply put, the Android TV market is still a tiny market. Google’s Nexus Player is most of the market right now, and only very recently have other Android TV devices such as the Forge TV and SHIELD Android TV reached the market.

As a result, figuring out what to compare the SHIELD Android TV to and how to present it has been an interesting challenge. A set top box is not a mobile device, and while they share similar OSes and the same families of SoCs, that does not make them identical devices. At the same time however, if we restrict ourselves to just Android TV devices, it would be a very limited and uninteresting comparison. The Nexus Player is a quad-core Intel Atom, but only includes 1GB of RAM, among other limitations.

Ultimately it’s clear that the SHIELD Android TV is heavily overspeced compared to other Android TV devices – no one else is pursuing this premium market – so instead we’re going to focus on looking at benchmarked performance relative to the newest generation of SoCs in the latest iOS and Android tablets. This is by no means a fair matchup and we need to be clear about this – the SHIELD Android TV has no throttling or power constraints, no need to balance out energy efficiency – but it at least gives us some idea of how the device and Tegra X1 compare to other products. Just don’t expect to see a Tegra X1 tablet perform this well. And in the meantime, some of the results may surprise you.

As always for an Android device review, we'll start off with our browser benchmarks. SHIELD Android TV doesn’t actually ship with a browser – we had to sideload Chrome – but these are among our most flexible benchmarks and help put performance in context of more than just Android devices.

Kraken 1.1 (Chrome/Safari/IE)

Google Octane v2  (Chrome/Safari/IE)

WebXPRT 2013 (Chrome/Safari/IE)

Among Android devices, the SHIELD Android TV stands alone, as you’d expect. Without any throttling to hold it back, it leads over Tegra K1, Snapdragon S810, and Exynos 7420 over all 3 web benchmarks. That said, even with its unrestricted Cortex-A57 CPU cores, we also find that Apple’s A8X-based iPad Air 2 is a close match in Octane and WebXPRT, just edging out the SHIELD Android TV and being edged out respectively. Meanwhile for anyone curious how this compares to high-end x86 tablets like the Surface Pro 3, well even SHIELD Android TV isn’t quite up to par with those devices at this time.

Moving on, we have Basemark OS II 2.0, which should give a better picture of CPU performance in addition to overall device performance.

Basemark OS II 2.0 - Overall

Basemark OS II 2.0 - System

Basemark OS II 2.0 - Memory

Basemark OS II 2.0 - Graphics

Basemark OS II 2.0 - Web

Overall, performance under Basemark still slightly favors the iPad Air 2. SHIELD Android TV easily takes the second spot, but it’s not enough to catch Apple’s tablet.

Looking at the subscores, we can see why this is. SHIELD Android TV only fares decently under the System test, but not well. The big surprise here is not the iPad, which always does well, but the fact that the SHIELD is so far behind the Galaxy S6, which features a similar CPU setup. As this sub-test pushes both the CPU and memory, we may be seeing something related to the implementation differences between Tegra X1 and Exynos 7420, or it may just be an Android TV-inspired difference.

However the memory score is particularly bad, coming in behind even the last-generation SHIELD Tablet. As this is a NAND test, what we're likely seeing is a consequence of the SHIELD's poor random performance, something we'll dive into a bit later in our detailed look at NAND performance.

On the other hand, graphics and web performance are outstanding. We had certainly expected the SHIELD to do well in graphics given what Maxwell is capable of – it is a graphics monster unlike any other current SoC – but the web test is a pleasant surprise. The combination of using Android TV’s built-in web view and the lack of any real throttling likely play a big part here, and although Android TV doesn’t ship with a standard web browser, this bodes well for any apps making use of web view and Javascript.

Our next system benchmark is PCMark, which does a number of basic benchmarks designed to stress various aspects of the device in everyday workloads like video playback, web browsing, text editing, and photo editing. This tends to test every aspect of a mobile device, unlike microbenchmarks that can often miss aspects of the system that can affect performance.

PCMark - Work Performance Overall

PCMark - Web Browsing

PCMark - Video Playback

PCMark - Writing

PCMark - Photo Editing

With the exception of the Writing subtest, where the SHIELD Android TV and second-place device are kind of close, PCMark is a runaway victory for the SHIELD Android TV. Once again we’re almost certainly seeing the benefits of the box’s aggressive performance since it doesn’t need to throttle down, or even be conservative on clockspeeds for power purposes. In which case it gives us an interesting look at what Cortex-A57 can do when not held back.

Overall, CPU/system performance is more or less what one would expect based on the design of the SHIELD. As a set top box with a quad-core A57 implementation under the hood and the cooling to let it run wild, SHEILD is frequently A57 at its best. Which means it’s going to easily surpass other A57 devices in most situations, but it also means that even with its unrestricted performance, Apple’s A8X processor and its tri-core “Enhanced Cyclone” CPUs still serve as a reminder of those times where A57 struggles against Enhanced Cyclone’s high-IPC design.

For our final look at system performance, let’s take a quick look at the SHIELD's built-in NAND performance with AndroBench 4.0.

AndroBench 4.0 - Sequential Read

AndroBench 4.0 - Sequential Write

AndroBench 4.0 - Random Read

AndroBench 4.0 - Random Write

Update 5/28: AndroBench numbers have been revised to account for an error, sorry about that

Though we only have a few AndroBench 4.0 results compiled so far, it’s enough to paint a decent picture. For sequential reads the SHIELD’s built-in NAND fares relatively well. It’s not enough to top the Galaxy S6 and its UFS flash, but it’s keeping up with the pack. Sequential writes on the other hand aren't quite as good, with write performance ahead of only the SHIELD Tablet. Meanwhile random performance is a real mixed bag; the SHIELD Android TV is at the bottom of the random read chart - below even the SHIELD Tablet - while random write performnace is significantly better than the tablet, but still chasing the M9 and well off the S6.

Among Android flagship devices UFS definitely gives the Galaxy a big benefit here, but the SHIELD could stand to improve all the same. However I’m not sure how much that matters to NVIDIA, as the SHIELD is clearly designed to lean on external storage via microSD/USB for users who end up using it for storage-intensive needs such as gaming as opposed to basic set top box streaming.

Tegra X1: The Heart Of the SHIELD Android TV Graphics Performance
Comments Locked

167 Comments

View All Comments

  • jeffkibuule - Thursday, May 28, 2015 - link

    Yeah, especially when you have controllers like the PS4 or Xbox One which do a far superior job in ergonomics, any other company that attempts to make a controller falls pretty flat on their face.
  • Brianbeastsu - Sunday, May 31, 2015 - link

    Have you used the shield controller yet? I personally had my doubts when I bought the tablet but its now my fav controller with the volume and mouse features I wish every controller had.....really awesome and could actually make the ps4 less of a nightmare if you ever wanted to think about using their browser.....ha......also the GRID streaming on the tablet is amazing so I will 100% be getting this....I didn't even know this existed until after I got the tablet and it blows anything else I've used out of the water....just my opinion
  • testbug00 - Thursday, May 28, 2015 - link

    19.2 watts of power? Cut off 2 A57 cores and one Maxwell SMM, I'm betting you would have one heck of a mobile chip for phablets and larger.
  • jt122333221 - Thursday, May 28, 2015 - link

    NVidia has chosen to chop off their mobile division and have openly stated they are no longer pursuing mobile devices like phones. Why would they gimp the chip to have a mobile chip when they aren't interested in mobile anymore?
  • testbug00 - Thursday, May 28, 2015 - link

    Not designing for a space and not having a product that can fit it are two different things. Over the course of all the runs for the X1 Nvidia might get enough "bad" chips to do a series that could fit into a phablet.

    Of course, for Nvidia's sake, I hope their yields don't allow for that :)
  • jeffkibuule - Thursday, May 28, 2015 - link

    Nvidia long ago stopped pursing phones because phone OEMs basically wanted chips with integrated LTE modems and Qualcomm had the best. Why go with a Tegra when you can get a Snapdragon that already has everything you need?
  • testbug00 - Friday, May 29, 2015 - link

    Tablet. End of story.
  • ZeDestructor - Friday, May 29, 2015 - link

    LTE tablets sell for a much larger margin, and it costs a hefty amount of engineering time to design two different platforms for the same product, then certify it, so they stick to the usual Qcomm stuff by and large.
  • ZOONAMI - Thursday, May 28, 2015 - link

    Can you please verify if the base 16gb model can be opened up so we can add our own SSD/HDD to it?
  • jt122333221 - Thursday, May 28, 2015 - link

    We will know in time - I guarantee someone will check by the end of next week.

Log in

Don't have an account? Sign up now