The State of JavaScript on Android in 2015 is... poor

Very nice results!! All kudos to Benedikt. Be sure to link him to your results via Twitter; I can’t as I am no longer on Twitter.

3 Likes

UPDATE: Reply from Benedikt

5 Likes

Good news! In the last year things have gotten a lot better!

Snapdragon 835, Android / Chrome circa June 2017

Snapdragon 845, Android / Chrome circa June 2018

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.

17 Likes

Using the newer more accurate (but lower) Speedometer 2.0 numbers here:

OnePlus 5 — Snapdragon 835 — 33.1
OnePlus 6 — Snapdragon 845 — 49.4
Xiaomi 9 — Snapdragon 855 — 68.5

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.

8 Likes

For comparison indicating that not all Snapdragon 835’s are the same:

Google Pixel 2 XL — Snapdragon 835 — 24.6

Updated to Android 10, full charge, plugged into mains after clean restart and waiting 5 minutes (so the phone isn’t busy starting).

The phone was originally released 23 months ago (Oct. 2017) and discontinued less than 6 months ago (April 2019).

4 Likes

Mine was tested months ago, closer to the time the hardware was originally made available. Ditto for the other model. The Xiaomi was tested yesterday :wink:

2 Likes

LG ThinQ G7 — Snapdragon 845 — 52.6
Chrome 77.0 Android 9, Speedometer 2

Gonna close this out with a bang

https://news.ycombinator.com/item?id=22878515

The Snapdragon 865 gets around 80-85 here, compared to…

13 Likes

I’ve seen strong improvements on Edge Canary on desktop though. i5-8265U that limits to 75-85 on stable Chrome v80, now hits 110 (+30%, on v84).

It mainly seems to be doing less work, since Intel Power Gadget doesn’t really show drastically different ‘CPU Util%’ (I’m guessing how many instructions could be retired by the execution units)

Not sure how this translates to ARM. Fingers crossed.

2 Likes

Desktop isn’t really a problem, we have massive amounts of perf. Improvements to Android are enormous though because of the weakness of the Qualcomm SoCs! Are you seeing any canary improvements on Android? :thinking:

Honestly iPhone 7 (855) and iPhone 8 / X performance (865) isn’t too bad on the Android side. It’s certainly “enough” from a Discourse perspective. It won’t blow you away but it’s totally competent.

2 Likes

My Meta PWA is running under 64-bits already :tada:

11 Likes

Note that you’re still looking at slightly-better-than-iPhone-7 perf on any new Android device, courtesy of Qualcomm. That is indeed an adequate level of performance for Discourse …

… but it is also … four years behind.

Also, data confirmed with my Xiaomi Mi 9 (Snapdragon 855) Android device, updated to latest everything:

8 Likes

Retesting this device now on Android 11, latest updates - now 22
image


And now the latest high-end phone from Google…
Google Pixel 5 - Snapdragon 765G - 25.5
image

7 Likes

iPhone 12 pro

12 Likes

iPhone 7 plus

4 Likes

Wow. That iPhone 12 Pro outperforms my fairly fancy new desktop with Core™ i7-10700F CPU @ 2.90GHz and a GPU (don’t know if that matters). That’s crazy.

8 Likes

Scores above 140 don’t really matter too much, if that helps :wink: … there’s a reason the graph “maxes out” at 140.

It’s the scores at ~70 and even lower that need some lovin’. And 70 is adequate for Discourse, for sure.

6 Likes

The iPhone 13 pro clocks a amazingly high 240, faster than any system I have ever seen

14 Likes

Retesting the Google Pixel 5 (same device) - 11 months later:

Gone from 25.5 to 31.2.
image

Latest (public) Android 11 OS / Chrome / software updates applied.

8 Likes

iPad Air is also amazing :heart_eyes:

3 Likes