Open Bug 1714541 Opened 3 years ago Updated 2 years ago

0.51 - 0.48% Base Content JS / Base Content JS + 4 more (Linux, OSX, Windows) regression on Wed June 2 2021

Categories

(Remote Protocol :: Marionette, defect, P3)

defect

Tracking

(firefox-esr78 unaffected, firefox-esr91 wontfix, firefox89 unaffected, firefox90 unaffected, firefox91 wontfix, firefox92 wontfix, firefox93 fix-optional)

Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- wontfix
firefox89 --- unaffected
firefox90 --- unaffected
firefox91 --- wontfix
firefox92 --- wontfix
firefox93 --- fix-optional

People

(Reporter: aesanu, Unassigned)

References

(Depends on 1 open bug, Regression)

Details

(Keywords: perf, perf-alert, regression)

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

Regressions:

Ratio Suite Test Platform Options Absolute values (old vs new)
1% Base Content JS linux1804-64-shippable 2,241,522.67 -> 2,252,912.00
1% Base Content JS windows10-64-shippable 2,251,837.33 -> 2,263,344.00
1% Base Content JS windows10-64-shippable-qr 2,251,837.33 -> 2,263,344.00
0.48% Base Content JS linux1804-64-shippable-qr 2,242,048.00 -> 2,252,832.00
0.48% Base Content JS macosx1015-64-shippable 2,242,989.33 -> 2,253,696.00
0.48% Base Content JS macosx1015-64-shippable-qr 2,242,989.33 -> 2,253,696.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?(hskupin)

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

The patch as landed on bug 1708532 fixed a 2ms delay during the content process startup. It's interesting that this is causing a higher memory usage. I assume the reason here is that we still have to load the Log, and the Marionette preferences modules. All in all this is a temporary workaround until we can make use of console.createInstance().

Jesup, is the increase of the memory usage here fine? Note that Marionette is not enabled by default when running Firefox, and so it actually doesn't contribute to higher memory usage. Feel free to redirect the needinfo if someone else has to answer the question. Thanks.

Flags: needinfo?(hskupin) → needinfo?(rjesup)
Priority: -- → P3

If the memory use is only when using marionette, that's fine.

Flags: needinfo?(rjesup)

Ok, so lets leave this bug open until the usage of console.createInstance() (bug 1712992) has been implemented.

Depends on: 1712992
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.