Closed Bug 1831833 Opened 2 years ago Closed 2 years ago

14.15 - 6.99% bing fcp / bing ContentfulSpeedIndex + 3 more (Android) regression on Tue May 2 2023

Categories

(Toolkit :: Form Autofill, defect, P1)

ARM64
Android
defect

Tracking

()

RESOLVED FIXED
115 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox113 --- unaffected
firefox114 --- fixed
firefox115 --- fixed

People

(Reporter: afinder, Assigned: issammani)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression, Whiteboard: [fxcm-bugs-2023])

Attachments

(2 files, 1 obsolete file)

Perfherder has detected a browsertime performance regression from push ca8b14caf6218ea583414dc768e186af73591886. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
14% bing fcp android-hw-a51-11-0-aarch64-shippable-qr cold webrender 376.90 -> 430.21
13% bing loadtime android-hw-a51-11-0-aarch64-shippable-qr cold webrender 404.71 -> 457.38
11% bing FirstVisualChange android-hw-a51-11-0-aarch64-shippable-qr cold webrender 487.12 -> 541.08
10% bing ContentfulSpeedIndex android-hw-a51-11-0-aarch64-shippable-qr cold webrender 760.08 -> 837.92
7% bing ContentfulSpeedIndex android-hw-a51-11-0-aarch64-shippable-qr cold webrender 780.38 -> 834.92

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the offending patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(imani)
Assignee: nobody → imani
Flags: needinfo?(imani)
Whiteboard: [fxcm-bugs-2023]

This performance regression is most likely caused by using static imports directly instead of lazy loading modules. I will open a patch for this. Please note that this is a patch that is required for a feature on iOS so backing this out might break things.

Set release status flags based on info from the regressing bug 1806951

:afinder just ran a performance test for bing on the new patch and compared results with an old patch. Performance seems to be up. Can you double check just to make sure ?

Flags: needinfo?(afinder)
Severity: -- → S2
Priority: -- → P1
Attachment #9332531 - Attachment description: WIP: Bug 1831833 - Import modules lazily where possible. r=#credential-management-reviewers! → Bug 1831833 - Import modules lazily where possible. r=#credential-management-reviewers!
Pushed by imani@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0494eb72005b Import modules lazily where possible. r=credential-management-reviewers,dimi
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
Flags: needinfo?(afinder)

The patch landed in nightly and beta is affected.
:issammani, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox114 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(imani)
Attachment #9333939 - Flags: approval-mozilla-beta?
Attachment #9333939 - Flags: approval-mozilla-beta?

I think we can uplift this to beta since it fixes a performance regression. I submitted an uplift request to beta.

Flags: needinfo?(imani)
Attachment #9333939 - Attachment is obsolete: true
Attachment #9333939 - Flags: approval-mozilla-beta-

Issam, when requestion an uplift to beta, there is a form to fill in with specific information, could you re-request and fill it in? Thanks

Flags: needinfo?(imani)

Uplift Approval Request

Hey Pascal, that's weird I remember filling it out before. In any case, I filled it out again. Let me know if any other steps are required from my end.

Flags: needinfo?(imani)
Attachment #9334139 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

(In reply to Issam Mani [:issammani] from comment #9)

I think we can uplift this to beta since it fixes a performance regression. I submitted an uplift request to beta.

Just writing to confirm that it did indeed resolve a performance regression :)
== Change summary for alert #38359 (as of Tue, 16 May 2023 22:05:26 GMT) ==

Improvements:

Ratio Test Platform Options Absolute values (old vs new)
12% bing FirstVisualChange android-hw-a51-11-0-aarch64-shippable-qr cold webrender 540.29 -> 474.75
11% bing fcp android-hw-a51-11-0-aarch64-shippable-qr cold webrender 434.52 -> 385.00
11% bing loadtime android-hw-a51-11-0-aarch64-shippable-qr cold webrender 464.04 -> 415.25
8% bing ContentfulSpeedIndex android-hw-a51-11-0-aarch64-shippable-qr cold webrender 835.42 -> 770.58
7% bing ContentfulSpeedIndex (geomean) android-hw-a51-11-0-aarch64-shippable-qr cold webrender 850.05 -> 787.78

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=38359

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: