lkwg82
(Lkwg82)
2016 年 3 月 29 日午後 7:58
1
Hi,
I experienced some (for me serious delays) in the rendering performance. For example this thread in the syncthing forum: SSL Certs discovery v4 vs v6 - General - Syncthing Community Forum .
I use the chrome on samsung s4.
(screenshot of developer tools), rendertime ~11s, without js ~1s (at home over wlan)
Thx in advance!
Falco
(Falco)
2016 年 3 月 29 日午後 8:02
2
I can be wrong but on a early 2013 phone, with 1.5GHz processor this is bad but kinda expected?
How is the timing loading meta.discourse.org and try.discourse.org ?
lkwg82
(Lkwg82)
2016 年 3 月 30 日午後 7:57
3
This phone has been 3years ago an high end phone. What is the phone distribution here on this site? Maybe there are less powerful phones.
Mobile design is IMHO not only about the responsive layout. It is also about speed/bandwidth and hardware limitations on these devices.
meta.discourse.org : http://www.webpagetest.org/result/160330_8K_592802ee00441a32192a5183af8ad1c9/
try.discourse.org : http://www.webpagetest.org/result/160330_49_024ca5619286ee2c338b3254e088d574/
forum.syncthing.org : http_://www.webpagetest.org/result/160330_YB_191aff8be451ac26636f4b115f2cc018/
You can see there is timerange with 100% cpu.
P.S. forum.syncthing is the fastest
Well, you have to take into account the speed of light here.
You are comparing the speed between Frankfurt San Francisco and Frankfurt Amsterdam.
Falco
(Falco)
2016 年 3 月 30 日午後 8:06
5
This tests are using the chrome emulation, and not real devices too.
http://mobitest.akamai.com/m/results.cgi?testid=160330_9W_3E
This gives 7s with a cold cache.
Discourse is working on improving this:
For several years now we’ve tracked the fact that, over time from 2012 onward, Android JavaScript performance has become wildly divergent from iOS JavaScript performance. And not in a good way.
To give you an idea of how divergent it has become, try:
http://emberperf.eviltrout.com
Complex list
Ember 1.11
This is the benchmark most representative of Discourse performance, and the absolute best known Android score for this benchmark is right at ~400ms on a Samsung Galaxy S6. That doesn’t seem …
lkwg82
(Lkwg82)
2016 年 3 月 30 日午後 8:17
6
ok, so you know about. I currently switched to the js-less version. At this point an app makes sense … a lot!
As of October 2017, JS perf in Android / Chrome is substantially improved, probably 1.5x - 2x speedup.
As of June 2018, Qualcomm has semi-competitive (iPhone 6s territory) hardware with the Snapdragon 845. It looks like their new release coming in 2019, the Snapdragon 855, will be close to iPhone 7 performance.
We do have to wait for the vast bulk of old Android devices to cycle through the market, unfortunately. I expect that will take another 4 years.
sam
(Sam Saffron)
2019 年 1 月 1 日午後 9:55
9
I find my really dodgy 50 dollar android somewhat usable these days
Falco
(Falco)
2019 年 1 月 1 日午後 9:56
10
For example I’m rocking a Pocophone F1 which costs $299, has the Snapdragon 845, and it’s a breeze to browse Discourse using it (I do it everyday )
Anything at Snapdragon 845 level or higher is going to be very solid for Discourse.
Shaneod
(Shane)
2019 年 7 月 23 日午前 7:44
12
AndroidのChromeブラウザを使用している数人のユーザーから、最近サイト読み込みが遅いという苦情が届いています。そのうち1人は、最後のアップデート以降のみです。これに影響を与えるような変更はありましたか?
最新バージョンであることを確認してください。リバースプロキシや Cloudflare のような特殊なプロキシの背後にある場合、最近、Brotli から gzip へのフォールバックが機能しないバグが発見されました。これにより生成されるペイロードファイルサイズを考えると、非常に苦痛です。
Shaneod
(Shane)
2019 年 7 月 23 日午後 1:03
14
すべて最新で、CDN やプロキシも使用していません。iPhone の Safari では正常に動作しています。同様の問題を抱えている方はいますか?インストールしているプラグインは広告用のもう一つだけで、現在は使用していません。