Closed Bug 1597229 Opened 5 years ago Closed 4 years ago

DAMP Perf regression on all devtools open tests (+2-5%, 10ms) due to additional panel triggering overflow menu

Categories

(DevTools :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jdescottes, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Regression from Bug 1594885.

The What's new panel impacted all existing open tests. The slowdown is about 10ms for each test.

This is either the cost of the additional tab to render, or the cost of isSupportedTarget:

  isTargetSupported: function(target) {
    // The panel is currently not localized and should only be displayed to
    // english users. See Bug 1596038 for cleanup.
    const isEnglishUser = Services.locale.negotiateLanguages(
      ["en"],
      [Services.locale.appLocaleAsBCP47]
    ).length;

    // In addition to the basic visibility switch preference, we also have a
    // higher level preference to disable the whole panel regardless of other
    // settings. Should be removed in Bug 1596037.
    const isFeatureEnabled = Services.prefs.getBoolPref(
      "devtools.whatsnew.feature-enabled",
      false
    );

    // This panel should only be enabled for regular web toolboxes.
    return target.isLocalTab && isEnglishUser && isFeatureEnabled;
  },
Summary: DAMP Perf regression on all devtools open tests (+2-5%, 10ms) → DAMP Perf regression on all devtools open tests (+2-5%, 10ms) because of What's new panel

Product was discussing hiding some of the less used panels (like the memory panel) by default, would that fix this regression?

(In reply to Panos Astithas (he/him) [:past] (please ni?) from comment #3)

Product was discussing hiding some of the less used panels (like the memory panel) by default, would that fix this regression?

It's very likely that the regression occurs because the panel goes into the "overflow" menu.
This depends on the browser size (1280px for DAMP), and it's not a real user facing regression.
We could fix the regression by hiding another panel, but if this theory is confirmed we can also simply accept the regression as the new baseline.

Probably a false alarm.

Attached image image.png

screenshot of DAMP running, as you can see next to the accessibility panel, we see the overflow menu icon, which means the What's New panel is overflowing and triggers the creation of this menu

Agreed, thanks Julian. I think it will be fair to treat this as a real regression if telemetry data shows a similar regression in the 95% of users after we ship (this window size might be more common than we think). Alternatively, if we have data on the most common window sizes and product can model the likely impact, we could consider that too.

I tried removing another panel (accessibility) and there is no clear performance impact. I think we can consider that the performance hit is purely due to the overflow menu. I think we should simply accept the hit and resolve as WONTFIX.

https://treeherder.mozilla.org/perf.html#/comparesubtest?originalProject=try&newProject=try&newRevision=c7886ca54d98016cc89ab11d462d6756d2d2c885&originalSignature=1759151&newSignature=1759151&framework=12&originalRevision=adbb8f47a9cc6091b1b4cf350c5db1534833052d

Unblocking the What's New meta.

No longer blocks: 1594879
Summary: DAMP Perf regression on all devtools open tests (+2-5%, 10ms) because of What's new panel → DAMP Perf regression on all devtools open tests (+2-5%, 10ms) due to additional panel triggering overflow menu

Bugbug thinks this bug is a defect, but please change it back in case of error.

Type: task → defect

This performance regression is only coming from the appearance of the overflow menu, no need to address this.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
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: