Google-maps recording is broken on mobile
Categories
(Testing :: Raptor, defect, P1)
Tracking
(firefox86 fixed)
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: sparky, Assigned: alexandrui)
References
Details
(Keywords: perf-alert)
Attachments
(3 files)
The google-maps recording is broken because it doesn't load up the actual map before finishing. It's either because of browsertime or the recording itself.
Reporter | ||
Comment 1•4 years ago
|
||
See this comment for some sample videos: https://bugzilla.mozilla.org/show_bug.cgi?id=1667938#c9
Comment 2•4 years ago
|
||
I don't know if this is the case here, but the --pageLoadStrategy", "none"
that we configure browsertime means that, to my understanding, we're not waiting for the load event. (We are only waiting for the root url to download and then 5 seconds).
This may not be sufficient for sites that populate asynchronously.
Reporter | ||
Comment 4•4 years ago
|
||
Yes, see the videos here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&selectedTaskRun=X7M11E8kT7662av10rwUCA.0&searchStr=google-maps&revision=abafe6c923eb566ffb94fd6afe0e06766d0c27a6
Assignee | ||
Comment 5•4 years ago
|
||
Assignee | ||
Comment 6•4 years ago
|
||
:sparky, I see no failing job in the screenshot attached.
Comment 7•4 years ago
|
||
(In reply to Alexandru Ionescu (needinfo me) [:alexandrui] from comment #6)
:sparky, I see no failing job in the screenshot attached.
This bug isn't about failing jobs, it's about the incomplete page load. You can download the browsertime-results.tgz from the job linked in comment 4 to see the problem described in comment 0.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
Assignee | ||
Comment 9•4 years ago
|
||
According to this comparison there will be some regressions, but giving the times were low because the map wasn't loading, it's expected.
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
bugherder |
Comment 12•4 years ago
|
||
== Change summary for alert #28120 (as of Thu, 17 Dec 2020 08:26:46 GMT) ==
Regressions:
Ratio | Suite | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|---|
121% | google-maps | SpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 849.75 -> 1,879.92 |
46% | google-maps | SpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,753.08 -> 2,556.42 |
44% | google-maps | fcp | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 441.75 -> 635.29 |
30% | google-maps | FirstVisualChange | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 740.75 -> 961.17 |
29% | google-maps | loadtime | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,495.54 -> 1,922.50 |
28% | google-maps | ContentfulSpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,685.75 -> 2,162.75 |
28% | google-maps | loadtime | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 996.62 -> 1,271.25 |
23% | google-maps | PerceptualSpeedIndex | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 880.17 -> 1,083.92 |
16% | google-maps | PerceptualSpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 862.38 -> 1,002.08 |
16% | google-maps | SpeedIndex | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 1,444.71 -> 1,672.58 |
16% | google-maps | PerceptualSpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 864.75 -> 1,000.42 |
14% | google-maps | ContentfulSpeedIndex | android-hw-p2-8-0-android-aarch64-shippable | cold nocondprof webrender | 1,188.29 -> 1,358.08 |
12% | google-maps | FirstVisualChange | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 426.96 -> 479.25 |
12% | google-maps | PerceptualSpeedIndex | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,746.25 -> 1,955.42 |
11% | google-maps | FirstVisualChange | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 806.17 -> 894.33 |
11% | google-maps | fcp | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 884.67 -> 981.33 |
9% | google-maps | FirstVisualChange | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,681.08 -> 1,836.33 |
Improvements:
Ratio | Suite | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|---|
60% | google-maps | LastVisualChange | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 4,102.50 -> 1,621.42 |
59% | google-maps | LastVisualChange | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 6,290.50 -> 2,550.92 |
58% | google-maps | loadtime | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 1,086.67 -> 460.75 |
47% | google-maps | loadtime | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 569.83 -> 300.96 |
46% | google-maps | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 839.34 -> 449.92 | |
36% | google-maps | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 450.30 -> 286.92 | |
33% | google-maps | LastVisualChange | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 6,313.92 -> 4,233.83 |
29% | google-maps | SpeedIndex | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 1,177.58 -> 834.08 |
29% | google-maps | ContentfulSpeedIndex | android-hw-p2-8-0-android-aarch64-shippable | nocondprof warm webrender | 918.92 -> 650.92 |
20% | google-maps | android-hw-g5-7-0-arm7-api-16-shippable | cold nocondprof webrender | 1,013.69 -> 807.90 | |
7% | google-maps | fcp | android-hw-g5-7-0-arm7-api-16-shippable | nocondprof warm webrender | 763.46 -> 713.08 |
For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=28120
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
•
|
||
Giving the previous recording wasn't loading the map, I would say that the regressions are expected. I'm a bit concerned about the 121% of SpeedIndex.
Reporter | ||
Comment 14•4 years ago
|
||
I wouldn't be concerned about the regressions even the 121% one. Here's a before/after video showing that everything's working now.
Description
•