Significantly different time required to navigate on local versus lab Android One devices |
|||||
Issue descriptionhttps://codereview.chromium.org/2576403005/ increased the navigation timeout for loading.mobile stories to 180s because some lab phones were exceeding the previous navigation deadline of 120s. To put this in practical terms: many of the pages included in the loading.mobile page set required more than two minutes to fully load. That seems *crazy*. What's strange, though, is that when I ran this test locally on my Android One device (Cherry Mobile G1, the same one that we use in the labs), pages that were exceeding the 120 second deadline in the lab took only 10 or 20 seconds to load on my local phone. Why are Android One phones in the lab having so much more trouble loading pages than the phone at my desk? The phone I have at my desk isn't flashed to the same version of Android, but it seems strange that a different version of Android might make page load take 6x longer. Unfortunately, I'm swamped with other tasks right now and don't have bandwidth to look into this, but it seems like it probably makes sense for someone to verify my findings and investigate this discrepancy.
,
Jan 6 2017
,
Jan 6 2017
,
Apr 20 2017
Android one devices are on svelte mode (i.e. pretend the device only has 512MiB); i.e.:
"ro.build.description": "sprout_svelte-userdebug 5.1.1 LMY47W 1837160 dev-keys",
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf__1_%2F5192%2F%2B%2Frecipes%2Fsteps%2Fdevice_status%2F0%2Flogs%2Fjson.output%2F0
Was your device also on svelte mode?
,
Jan 16
,
Jan 16
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by charliea@chromium.org
, Jan 6 2017