Closed Bug 1743893 Opened 2 years ago Closed 2 years ago

1.65 - 1.38% Base Content JS / Base Content JS + 2 more (Linux, OSX, Windows) regression on Mon November 29 2021

Categories

(Core :: Privacy: Anti-Tracking, defect)

defect

Tracking

()

RESOLVED FIXED
97 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox94 --- unaffected
firefox95 --- unaffected
firefox96 --- disabled
firefox97 --- fixed

People

(Reporter: aglavic, Assigned: timhuang)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a awsy performance regression from push 385267bb6f1bb85642b568d873a6231b73600c0a. 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)
2% Base Content JS macosx1015-64-shippable-qr 1,830,168.00 -> 1,860,408.00
1% Base Content JS windows10-64-2004-shippable-qr 1,808,504.00 -> 1,833,576.00
1% Base Content JS windows10-64-2004-shippable-qr 1,808,448.00 -> 1,833,560.00
1% Base Content JS linux1804-64-shippable-qr 1,803,167.33 -> 1,828,136.00

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

The regression is because we start loading the URLQueryStrippingListService.jsm during the startup of content processes. We have opened bug 1743418 to improve the situation and I plan to implement it in the next release. Also, this will only affect the Nightly channel because the query stripping is currently only enabled in the Nightly channel. Therefore, I think the regression won't be a problem in short term.

Flags: needinfo?(tihuang)

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

Depends on: 1743418

Given that Bug 1743418 was fixed, could we verify if the regression was fixed?

Flags: needinfo?(aglavic)

An improvement alert has appeared for that Bug 1743418, we verified that the regression was fixed!

It had the following improvements:
== Change summary for alert #32718 (as of Tue, 14 Dec 2021 18:13:13 GMT) ==

Improvements:

Ratio Test Platform Options Absolute values (old vs new)
1% Base Content JS linux1804-64-shippable-qr 1,822,548.00 -> 1,812,018.00
1% Base Content JS macosx1015-64-shippable-qr 1,850,707.64 -> 1,840,904.00
0.48% Base Content JS linux1804-64-shippable-qr 1,820,482.67 -> 1,811,832.00
0.47% Base Content JS windows10-64-2004-shippable-qr 1,825,922.67 -> 1,817,256.00

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

Flags: needinfo?(aglavic)

Given comment 4, I think we can resolve this bug.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Assignee: nobody → tihuang
Target Milestone: --- → 97 Branch
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.