Closed Bug 1720072 Opened 3 years ago Closed 3 years ago

100 - 35.55% tp5o_webext XRes / cpstartup content-process-startup + 4 more (Linux) regression on Tue July 6 2021

Categories

(Testing :: Talos, defect)

Firefox 91
defect

Tracking

(firefox-esr78 disabled, firefox90 disabled, firefox91 fixed, firefox92 fixed)

RESOLVED FIXED
92 Branch
Tracking Status
firefox-esr78 --- disabled
firefox90 --- disabled
firefox91 --- fixed
firefox92 --- fixed

People

(Reporter: alexandrui, Assigned: jld)

References

(Regression)

Details

(4 keywords)

Attachments

(1 file)

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

Improvements:

Ratio Suite Test Platform Options Absolute values (old vs new)
100% tp5o XRes linux1804-64-shippable-qr e10s stylo webrender 198,823.46 -> 0.00
100% tp5o XRes linux1804-64-shippable-qr e10s stylo webrender-sw 6,486,677.36 -> 0.00
100% tp5o_webext XRes linux1804-64-shippable-qr e10s stylo webrender-sw 6,484,976.28 -> 0.00
100% tp5o_webext XRes linux1804-64-shippable-qr e10s stylo webrender 198,850.89 -> 0.00
39% cpstartup content-process-startup linux1804-64-shippable-qr e10s stylo webrender 100.33 -> 61.25
36% cpstartup content-process-startup linux1804-64-shippable-qr e10s stylo webrender-sw 96.33 -> 62.08

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?(jld)

Looks like a bug in [the testing code here]: content processes will generally no longer show up in xrestop output because they're not using X, so that should continue the loop instead of throwing an exception. (They may still appear if WebGL is active when the sample is taken.)

It looks like that exception is caught here and discarded, which would explain why the Could not find PID message doesn't appear in the logs.

Note that the cpstartup changes are an improvement, and expected.

I'll take the bug; it should be simple.

Assignee: nobody → jld
Component: Widget: Gtk → Talos
Flags: needinfo?(jld)
Product: Core → Testing

Should we uplift this fix to Beta 91? Semi-headless mode is riding the trains in Fx91, but I don't know if we monitor Talos performance in channels other than mozilla-central/Nightly.

Pushed by jedavis@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8fe683c45800
Allow the XRes perf metric to tolerate content processes not using X11. r=perftest-reviewers,AlexandruIonescu
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch

Alexandru, should we uplift Jed's Talos cmanager_linux.py fix to Beta 91? Do we run Talos on Beta builds?

Flags: needinfo?(aionescu)

(In reply to Chris Peterson [:cpeterson] from comment #6)

Alexandru, should we uplift Jed's Talos cmanager_linux.py fix to Beta 91? Do we run Talos on Beta builds?

Seems like we do.

Flags: needinfo?(aionescu)

The patch landed in nightly and beta is affected.
:jld, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.

For more information, please visit auto_nag documentation.

Flags: needinfo?(jld)

Comment on attachment 9230781 [details]
Bug 1720072 - Allow the XRes perf metric to tolerate content processes not using X11.

Beta/Release Uplift Approval Request

  • User impact if declined: Missing performance metrics. (We track these on m-c and beta, but apparently not release or ESR.)
  • 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: Run Talos tp5o on Linux; check if the XRes metric is 0 (it shouldn't be).
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): NPOTB: affects only performance test code
  • String changes made/needed: none
Flags: needinfo?(jld)
Attachment #9230781 - Flags: approval-mozilla-beta?

Comment on attachment 9230781 [details]
Bug 1720072 - Allow the XRes perf metric to tolerate content processes not using X11.

Approved for 91 beta 5, thanks.

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

Attachment

General

Created:
Updated:
Size: