Closed Bug 1944853 Opened 1 year ago Closed 1 year ago

2.84% vpl-h264 lastFrame (OSX) regression on Thu January 16 2025

Categories

(Core :: Audio/Video: Playback, defect)

Desktop
macOS
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox134 --- unaffected
firefox135 --- unaffected
firefox136 --- wontfix
firefox137 --- wontfix

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push a48c549c0975d3d4f8047532a38228e5d151b1bc. 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) Performance Profiles
3% vpl-h264 lastFrame macosx1470-64-shippable cold fission webrender 1,155.94 -> 1,188.76 Before/After

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 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.

You can run all of these tests on try with ./mach try perf --alert 43539

The following documentation link provides more information about this command.

For more information on performance sheriffing please see our FAQ.

If you have any questions, please do not hesitate to reach out to fbilt@mozilla.com.

Flags: needinfo?(alwu)

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

Flags: needinfo?(alwu) → needinfo?(aosmond)

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

I think we're ok here. I'll let Alastor comment on the slight regression in lastFrame. firstFrame tests didn't regress. These tests measure the time it takes Firefox to display a particular frame of video. First frame is obviously the most important. Last frame might indicate some sort of added overhead in video display or a shifting of existing overhead, so we want to look at it to understand why.

Severity: -- → S3
OS: Unspecified → macOS
Hardware: Unspecified → Desktop
Version: unspecified → Trunk

It has been over 7 days with no activity on this performance regression.

:alwu, since you are the author of the regressor, bug 1941890, which triggered this performance alert, could you please provide a progress update?

If this regression is something that fixes a bug, changes the baseline of the regression metrics, or otherwise will not be fixed, please consider closing it as WONTFIX. See this documentation for more information on how to handle regressions.

For additional information/help, please needinfo the performance sheriff who filed this alert (they can be found in comment #0), or reach out in #perftest, or #perfsheriffs on Element.

For more information, please visit BugBot documentation.

Flags: needinfo?(alwu)

I think we have to live with this.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(aosmond)
Flags: needinfo?(alwu)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.