System Performance

To see how the new CPUs and memory subsystem translate into more real system performance, we move onto more representative tests such as PCMark. PCMark’s performance is affected by several factors: not only does raw performance of the hardware count but also we need to consider the individual system’s software stack. We’ve seen large differences between Android OS major versions where the improvements of the Android Runtime can be directly visible in subtests such as the Writing test. Also a SoC’s DVFS schemes and schedulers can have huge impacts on “performance-latency”, meaning how fast the CPUs can ramp up a workload. This directly translates in a lot more performance in several of PCMark’s subtests as in the default settings none of the tests actually represent the pure performance of the CPU if it were locked at maximum frequency on the performance cores. The results of the tests are also overall a good representation of “snappiness” of a device.

PCMark Work 2.0 - Web Browsing 2.0

In the web browsing test the Snapdragon 845 QRD manages to outpace the Pixel 2 XL by 20%. Here we’re also looking at performance across devices with different OS versions. The Google devices are running Android 8.1 while the Samsung devices were tested with Android 7.0. The Mate 10 Pro runs Android 8.0 while the Mate 9 still had 7.0. The Qualcomm QRD we tested ran Android 8.0.

Again the performance increase over Snapdragon 835 devices isn’t all that great. DynamiQ allows for far more efficient thread transitions between the CPU cores and subsequently I expected Qualcomm to take advantage of this through more aggressive scheduling resulting in more than just a 20% increase. The difference between the Mate 9 and Mate 10 here is a good example of what a software configuration change can bring in terms of performance (both devices employ same performance CPU configurations). Samsung’s Exynos’ SoCs still use GTS scheduling and have non-optimal performance-latency resulting in bad scores, amplified by the fact that Samsung’s memory performance is also underwhelming when compared to the Snapdragon and Kirin SoCs.

PCMark Work 2.0 - Data ManipulationPCMark Work 2.0 - Writing 2.0

The Data Manipulation and Writing 2.0 tests make heavy use of the Android runtime and APIs and also a very memory latency sensitive. Between the best showings of the Snapdragon 835 variant of the S8 and the Pixel 2 XL in each respective benchmark, the Snapdragon QRD845 showed conservative increases of 8 to 14%. The Exynos SoCs lacklustre performance is again hampered by software and by bad memory performance.

PCMark Work 2.0 - Video Editing

The video editing test is PCMark’s weak-point as it’s bottlenecked by things such as OS API overhead, and why we see tight grouping of performance results across a large range of SoCs. The Snapdragon 845 ends up high, but below the Pixel 2 XL. I would not put much weight on the results of this test as they’re not necessarily representative. Futuremark claims that the test is a lot more sensitive in mid- and low-range devices which can exhibit performance issues.

PCMark Work 2.0 - Photo Editing 2.0

The photo editing test makes heavy use of Renderscript and use GPU acceleration to apply various effects on an image set. The QRD845 here shines as it’s able to showcase a 38% performance improvement over the Pixel 2 XL. Again the test not solely tests the raw performance of the system but also how optimized it is in terms of the software stack. This can be seen in the Kirin vs Exynos devices as Huawei’s phones vastly outperform Samsung’s devices in this test.

PCMark Work 2.0 - Performance

Overall PCMark’s performance score for the QRD845 increases by 17% over the Pixel 2 XL. Disregarding the video test, we see a similar scenario as in the synthetic tests as the new SoC’s CPU performance increases are lower than we had expected. Still the Snapdragon 845 is able to top the charts and should adequately power 2018’s flagship devices.

For 2018 we are reviewing our mobile benchmarking suite and altering some of the benchmarks we use. One of the changes in the way we benchmark devices is that we’re moving away from standalone browser and rather are benchmarking the OS’s WebView implementations. In general this seems to be a better choice for testing device experience as there is a lot of content that is being consumed via WebView windows. We also avoid the argument about different browser performance and since Google has now made WebView an updatable Play Store component we should also have valid comparisons older devices and systems. On the iOS side we do the same as we now benchmark browser tests within a WkWebView shell.

WebXPRT 2015 - OS WebView

Starting off with WebXPRT 2015 for a last time before we’ll retire it in favour of WebXPRT 3, we see the QRD845 performing fantastically. Here the 44% performance increase over the Pixel 2 XL is a lot more in line with what we had expected of the new SoC. The QRD845 is even able to catch up a lot with Apple’s newest A11 and Monsoon cores in this test.

To keep up with the ever changing landscape of the developing web, we’re also retiring past JavaScript benchmarks in favour of a brand new and more representative benchmark developed by the WebKit team and welcomed by Google; Speedometer 2.0.

Speedometer 2.0 - OS WebView

Here the Snapdragon 845 showcased another healthy performance increase of 37% over the Snapdragon 835 devices. Apple’s superior JavaScript performance can be attributed to a much faster and more optimized Nitro engine while Google’s V8 has only seen meagre improvements over the years. Notable is the Apple A11’s massive performance jump over the A10 – vastly increasing the distance to Android devices.

CPU & Memory Subsystem GPU Performance & Power Estimates


View All Comments

  • close - Tuesday, February 13, 2018 - link

    A11 does pretty well for a SoC that has only 2 high performance cores, versus the 835's 4.

    So shake it harder. maybe something good comes out :).
  • lilmoe - Tuesday, February 13, 2018 - link

    Enjoy your 2 high performance cores at 600mhz, cute little iFan, since that's max clock speed it can go and still be relatively efficient, at least according to Apple. Reply
  • techconc - Wednesday, February 14, 2018 - link

    Wow, this is certainly one of the more delusional posts I've ever seen. The A11 is head and shoulders above the SD835. It's not even close. What's worse, this is the period where the Qualcomm is supposed to match or exceed Apple's chip. Outside of 3D Mark anomaly, that doesn't appear to have happened. Reply
  • Matthmaroo - Saturday, February 17, 2018 - link

    dude Do you really believe your own crap Reply
  • Eximorph - Tuesday, February 13, 2018 - link

    Sorry to disappoint you but apple is probably ahead on the cpu but on the gpu is still behind and for like 3 years. The A11 gpu score 2475 vs my lg g5 with adreno 530 score 2545. IPhone 8 slingshot Reply
  • techconc - Wednesday, February 14, 2018 - link

    I guess it depends on the benchmark you use to make your claim. The GFXBench scores seem to clearly favor the A11. Reply
  • Eximorph - Thursday, February 15, 2018 - link

    Yep beacuse the a11 only can use old and light api's like open gl es 2.0 or 3.0 but not 3.1 or 3.2 like android do it. Even the adreno 530 run's them like a champion. Reply
  • techconc - Friday, February 16, 2018 - link

    Apple still keeps legacy support for OpenGL but has moved on to Metal. At the end of the day, it's how fast it performs a task that matters, not which API it's using. Maybe someday when Vulkan matures a bit and enough of the Android user base gets on a modern Android OS release there will be some level of API parity, but not today. Reply
  • Matthmaroo - Saturday, February 17, 2018 - link

    Lol android and parity across devices

    Almost every android phone is abandoned by manufacturers after 6 months
  • Eximorph - Tuesday, February 20, 2018 - link

    You are wrong hahha is 2 years but different from apple android manufacturer's do not reduce you processor speed beacus a cheap battery hahahah and bad battery life. Reply

Log in

Don't have an account? Sign up now