Closed Bug 1648687 Opened 4 years ago Closed 4 years ago

16.44 - 2809.13% perf_reftest (linux64-shippable|-qr, macosx1014-64-shippable, windows10-64-shippable|-qr, windows7-32-shippable) regression on push ce5cdfc5d7cfb19af1044a5e1b7e93eedeb5e8be (Tue June 23 2020)

Categories

(Core :: Panning and Zooming, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox77 --- unaffected
firefox78 --- unaffected
firefox79 --- disabled
firefox80 --- fixed

People

(Reporter: alexandrui, Assigned: kats)

References

(Regression)

Details

(4 keywords)

Attachments

(1 file)

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

Regressions:

2809% perf_reftest recompute-position-vertical-rl.html macosx1014-64-shippable opt e10s stylo 0.42 -> 12.22
2167% perf_reftest recompute-position-vertical-rl.html linux64-shippable opt e10s stylo 0.48 -> 10.81
1726% perf_reftest recompute-position-vertical-rl.html windows10-64-shippable opt e10s stylo 0.57 -> 10.47
1661% perf_reftest recompute-position-vertical-rl.html windows7-32-shippable opt e10s stylo 0.68 -> 11.97
1446% perf_reftest recompute-position-vertical-rl.html linux64-shippable-qr opt e10s stylo 0.77 -> 11.83
1427% perf_reftest recompute-position-vertical-rl.html windows10-64-shippable-qr opt e10s stylo 0.73 -> 11.09
20% perf_reftest windows10-64-shippable-qr opt e10s stylo 1.48 -> 1.77
20% perf_reftest windows7-32-shippable opt e10s stylo 1.37 -> 1.65
16% perf_reftest windows10-64-shippable-qr opt e10s stylo 1.52 -> 1.77

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) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(kats)
Component: Performance → Panning and Zooming
Product: Testing → Core

(In reply to Alexandru Ionescu (needinfo me) [:alexandrui] from comment #0)

Perfherder has detected a talos performance regression from push ce5cdfc5d7cfb19af1044a5e1b7e93eedeb5e8be.

This push is for a different bug with a different author. Can you clarify which one is the correct push?

Flags: needinfo?(kats) → needinfo?(aionescu)

Looks like cc56a4cc04156b0c58944eb32ddf4f9592d2c0cd is the culprit, which is not unreasonable. The work I'm doing in bug 1647034 will probably help some. If it doesn't fix it entirely I can investigate more at that point.

Assignee: nobody → kats
Severity: -- → S3
Depends on: 1647034
Flags: needinfo?(aionescu)
Priority: -- → P3

Also as a fallback plan for uplift to 79 (since we're about to switch to 80 on nightly) we should be able to turn off apz.mvm.force-enabled and readjust the necessary crashtest assertions. I did a try push that shows it's green for correctness, and I've scheduled the perf-reftest talos jobs on it to verify it will fix the regressions.

With bug 1647034 on autoland I see the graphs going back to their previous values. So I'll close this bug once that merges to m-c. However for uplifting to 79 I'll make a patch to disable the MVM pref, because I think that's a safer fix than uplifting the new patches that landed on 80.

This is the low-risk fix for landing on beta 79 to restore original
performance.

Comment on attachment 9160394 [details]
Bug 1648687 - Disable the visual-viewport-only MVM for beta 79. r?tnikkel

Beta/Release Uplift Approval Request

  • User impact if declined: Slight performance regression
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Disables the code that introduced the performance regression. Note that the regression has been fixed in 80 but it's safer to disable the offending code than to uplift the fixes for fixing the perf regression in 79.
  • String changes made/needed:
Attachment #9160394 - Flags: approval-mozilla-beta?
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: mozilla79 → mozilla80

Comment on attachment 9160394 [details]
Bug 1648687 - Disable the visual-viewport-only MVM for beta 79. r?tnikkel

Approved for 79.0b2, thanks.

Attachment #9160394 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: