System Performance Cont'd

Now that we've covered more general purpose benchmarks that tend to emphasize CPU performance and GPU compute performance, we can look at benchmarks that tend to more strongly emphasize things that games will see benefits from such as improved GPU graphics performance and improved CPU physics processing performance.

GFXBench Car Chase ES 3.1 / Metal (On Screen)

GFXBench Manhattan ES 3.1 / Metal (On Screen)

GFXBench Car Chase ES 3.1 / Metal (Off Screen 1080p)

GFXBench Manhattan ES 3.1 / Metal (Off Screen 1080p)

Basemark ES 3.1 / Metal

Basemark ES 3.1 / Metal Offscreen Test

Basemark ES 3.1 / Metal Onscreen Test

It's probably no surprise, but the Galaxy Note7 performs as expected with the latest drivers and in ideal thermal conditions. The Adreno 530 should be more than sufficient for the forseeable future but for maximum performance it's best to enable 1080p rendering or lower to maximize frame rates in games like Real Racing 3 that tend to really use the GPU to its fullest extent.

NAND Performance

Of course, while Discomark provides a sort of holistic view of performance for a specific task, it’s also important to at least try and break down the various aspects that impact system performance so rather than simple black box testing we can further understand what factors influence performance and therefore provide additional information to make better buying decisions. One of the major contributors to general purpose performance is going to be storage performance, which is often something often ignored by marketing as the nitty gritty details of NAND storage realistically require some background in solid state physics and devices to understand, as well as some understanding of computer science and engineering.

While I’m not really happy with the state of our mobile storage benchmarks, for now I don’t really see another option here as the publicly available storage benchmarks for Android and iOS are fairly basic. Putting aside the state of the benchmarking industry, our current benchmark remains AndroBench 4 which provides at least some basic storage benchmarking capabilities. We use custom settings with this benchmark which attempts to make the test more realistic as the default settings are just wildly unrealistic. This includes adjusting the buffer size, increasing the file size to 100 MB, and only using one thread instead of 8. 256KB file size is targeted as this is the most common block size if you profile this kind of thing for sequential writes and reads, while 4KB block sizes are the most common for other tasks as the vast majority of computer architectures use 4KB pages for virtual memory. Single-threaded I/O is common in most cases because multi-threaded programming is still difficult for most people to reason about in an effective manner because conscious thought is inherently serial in nature with some multiplexing. In addition to this, many eMMC solutions on the market don’t really perform well with multiple threads simultaneously as the controller can’t do anything with extra requests other than reply with a busy signal which already happens with a single thread.

Putting aside discussions of testing we can take a look at the storage solution used in the Galaxy Note7 before getting into the actual results. The Note7 continues to use basically the same storage solution as the Galaxy S7 and S6, which is to say an MLC-based solution that has a UFS Gear 3 single lane interface for bandwidth up to 600 MB/s and basically has the exact same model number if you check the SCSI devices attached to the system save for some changes that indicate the higher 64GB storage relative to the 32GB chips that are most common in the Galaxy S7.

Androbench 4.0 - Squential Read

AndroBench 4.0 - Sequential Write

AndroBench 4.0 - Random Read

AndroBench 4.0 - Random Write

Looking at the test results it performs exactly as quickly as you’d expect from this MLC solution as we’ve tested it in the Galaxy S6, S6 edge, S6 edge+, Note5, S7, S7 edge, and now the Note7 as well as the LG G5. The performance here is acceptable but obviously if you look at burst performance the iPhone 6s has a faster solution due to the hybrid SLC/TLC storage solution. The main benefit of pure MLC NAND is that performance is more consistent as there’s no precipitous drop when the SLC buffer fills. There’s always room to improve but I don’t really see how it’s going to happen unless Samsung moves to V-NAND for the next generation.

System Performance Camera Architecture and UX
Comments Locked

202 Comments

View All Comments

  • JoshHo - Tuesday, August 16, 2016 - link

    That is unlikely as the charging current is already limited if the screen is on with the Galaxy Note7 and S7.
  • Tigran - Tuesday, August 16, 2016 - link

    No throttling test?
  • JoshHo - Tuesday, August 16, 2016 - link

    Due to time constraints it couldn't be run. I will update the review when possible with the results as well as a pipeline post.
  • vanilla_gorilla - Tuesday, August 16, 2016 - link

    "My major complaint here continues to be a general lack of performance as things like scrolling don’t feel like they have the momentum or response that they should and I still see frame drops that don’t happen in comparable devices."

    How is this still possible?
  • damianrobertjones - Tuesday, August 16, 2016 - link

    It needs another 8 CPUs
  • shabby - Tuesday, August 16, 2016 - link

    Because snapdragon, the s7 exynos version was smoother than the sd820 version.
  • grayson_carr - Tuesday, August 16, 2016 - link

    The SD820 actually has the power to run the UI more fluidly than the Exynos. The Moto Z runs extremely fluidly, even moreso than the Exynos S7. The problem is, Samsung optimizes the kernel / governor settings on SD820 devices more for battery life than for performance.
  • arayoflight - Tuesday, August 16, 2016 - link

    And yet the exynos destroys it in battery.
  • grayson_carr - Tuesday, August 16, 2016 - link

    Yeah. The Exynos is more efficient. But performance is still less than it should be because of Samsung's bloated software and prioritization of battery life. The Moto Z runs circles around the Exynos S7 in real world smoothness, even though the Exynos is a better chip than the SD820. Stop making this about Exynos vs Snapdragon. This is about Samsung's crappy software and optimization regardless of what chip is used.
  • niva - Tuesday, August 16, 2016 - link

    Ding ding ding, you said it. Samsung's bloated software.

    TouchWiz is an abomination that should be destroyed by fire. Each year they tout how amazing the new TouchWiz is going to be without telling you the performance penalty it brings. These overlays should only be allowed as apps that one can disable.

    If say stick to Nexus devices but in this case it's the only good phablet and there are no nexuses with pen support. Suffer through TouchWiz is your only option

Log in

Don't have an account? Sign up now