Impressively, I just tested @zogstrip’s Nexus 6p on emberperf.eviltrout.com, render complex list, 2.11 and I got ~150ms. That’s quite good.
Chrome 55
212 ms
Chrome 58
175 ms
Chrome 61
150ms
That puts it in iPhone 6 territory, which is about where it should be based on the CPU, and I would rate it as solidly “good”. The Nexus 6p is not exactly a new device… we’ll see where Snapdragon 845 takes us. Current rumors say:
The Snapdragon 845 scores 2600+ in GeekBench 4, for single core results.
For those that are not familiar with why Apple devices show higher performance and why Android device manufacturers appear to be playing catch-up here is a nice video with a little bit of history:
For point of reference I ran some of the benchmarks on my OnePlus 2 (ONE A2003) an August 2015 Qualcomm Snapdragon 810 phone - the same processor as the Nexus 6P mentioned above.
This was a new phone when this thread was started back in 2015, now updated the phone running on a custom Lineage OS build (Android 7.1.2). In a months time a replacement phone will come and I’ll reset the device to whatever the latest manufacturer OS is and run these numbers again.
Canary isn’t a good test candidate. Try beta. Canary is too variable. Also you don’t need both runs, the HTML and regular are pretty much the same these days.
I wanted to check if this repeatable cross another device…
Trying it on a slightly older (from the factory, OEM updates only) “OnePlus One” (A0001) - Qualcomm Snapdragon 801 - Cyanogen OS 13.1.2 - Android 6.0.1 phone - released April 2014.
Note this is Speedometer 1.0 to keep the comparison apples to apples. Between the respectable hardware bump (finally) and major Chrome/Android JS improvements, we’re looking at 2x improvement. Vastly overdue… but I’ll take it!
This is finally iPhone 6s territory which I’d call certainly fast enough for native Discourse performance.
These are of course quite far from iOS hardware numbers, kind of vaguely iPhone 7-ish. For comparison this iPad Pro gets 137.5 and the iPhone 11 gets around 150.
J’ai cependant constaté de nettes améliorations sur Edge Canary pour le bureau. Un i5-8265U qui plafonnait à 75-85 points sur Chrome stable v80 atteint désormais 110 (+30 %, sur la v84).
Il semble principalement effectuer moins de travail, car Intel Power Gadget ne montre pas de différence drastique au niveau du « CPU Util% » (je suppose qu’il s’agit du nombre d’instructions pouvant être terminées par les unités d’exécution).
Je ne sais pas comment cela se traduira sur ARM. Croisons les doigts.
Le bureau n’est vraiment pas un problème, nous avons d’énormes gains de performance. Les améliorations sur Android sont considérables, en raison de la faiblesse des SoC Qualcomm ! Voyez-vous des améliorations dans la version Canary sur Android ?
Honnêtement, les performances de l’iPhone 7 (855) et de l’iPhone 8 / X (865) ne sont pas si mauvaises du côté Android. C’est certainement “suffisant” d’un point de vue Discourse. Cela ne vous épatera pas, mais c’est tout à fait compétent.
