Closing the app and re-launching it caused it to again no longer work on the Cortex-X1 cores, and only run on the Cortex-A78 cores – this time around at the full 2.41GHz. What’s utterly perplexing however, is that while this score was repeatable back-to-back, it was only ever achievable on a fresh installation of the browser. We’ll get into more detail a bit later about browsers – but the only way I ever managed to achieve the full performance of the Snapdragon 888 and have the X1 cores being loaded in the benchmark was in Vivaldi, resulting with a score of 107 which is in line with other Snapdragon 888 phones. What’s more perplexing, is that when re-running the test immediately again in sequence, the workload is now being completely isolated to the little Cortex-A55 cores, with an expectedly horrible score of 16.8. Furthermore, these are running at only 2GHz instead of their maximum 2.41GHz. Monitoring the CPU’s behaviour during the run points out that the system is never loading the Cortex-X1 core of the Snapdragon 888, and instead is running the benchmark on the Cortex-A78 cores. During the first run, the phone is managing a score of 61.5 – a low score that’s very abnormal for a Snapdragon 888. In the first/left video – I’m starting Chrome fresh and running the browser-based Speedometer 2.0 benchmark. In particular, Chrome seemed to be suffering from extremely weird behaviour that at worst ended up with the browser only being able to use the SoC’s little Cortex-A55 cores. OnePlus 9 Pro - Chrome & Vivaldi Performance In testing, I had encountered something which really perplexed me, and caught my attention seemingly inexplicable slow browser benchmark figures which were not in line with any other Snapdragon 888 device in the market, getting only a fraction of the scores and performance of other devices. The OnePlus 9 Pro was released in early April, however due to other work in the pipeline we never got to fully review the phone until now – well, that’s also a bit delayed due to today’s piece. Starting off with weird benchmark numbersĪs always with these stories, it all starts out when discovering some weird oddity when going over the usual review process. This is perhaps to improve battery life at the expense of performance, but it does mean that the regular benchmark results are somewhat useless for user experience. ![]() We have confirmed that (a) benchmarks or (b) unknown apps get full performance most of the top popular non-benchmark apps get notably reduced performance. We have detected that OnePlus is blacklisting popular applications away from the its fastest cores, causing slow down in typical workloads such as web browsing. ![]() It’s something so unusual and baffling, as it truly blurs the line between battery optimisation, performance cheating, and general device specification misrepresentation. Today’s piece fits within this class of articles, and more specifically covers OnePlus’ newest OnePlus 9 Pro flagship phone, and how its performance behaviour indeed manages to be extremely unique in the current mobile landscape. They're (Almost) All Dirty: The State of Cheating in Android BenchmarksĮvery now and then, these topics always resurface as vendors attempt to “differentiate” their devices amongst the crowd – it’s a repeated process which unfortunately by now no longer really surprises us when it happens. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |