Closed Bug 1953893 Opened 1 year ago Closed 1 year ago

Create/update performance components

Categories

(bugzilla.mozilla.org :: Administration, task)

Production

Tracking

()

VERIFIED FIXED

People

(Reporter: davehunt, Assigned: dkl)

Details

In order to improve the triage of performance related bugs, we would like to make the following changes to components:

  • Create component Performance: Startup in the Core product:
    • Description: Issues related to browser startup. Including any issues that occur directly after startup and that are expected to be related to startup activities.
    • Triage owner: Denis Palmeiro
  • Create component Performance: Responsiveness in the Core product:
    • Triage owner: Markus Stange
    • Description: Issues related to responsiveness when interacting with content on websites without navigating to different pages. (For example zooming or panning Google Maps)
  • Create component Performance: Navigation in the Core product:
    • Triage owner: Andrew Creskey
    • Description: Issues related to both hard and soft navigations on the web.
  • Create component Core::Performance: Memory in the Core product:
    • Triage owner: Justin Link
    • Description: Issues related to excessive browser memory usage, including when the memory usage is responsible for direct performance degradation.
  • Create component Performance in the Firefox product:
    • Triage owner: Mike Conley
    • Description: Issues related to the performance of the browser front-end.
  • Rename component Performance in the Core product to Performance: General
    • Change triage owner to: Bas Schouten
    • Change description to: Issues related to Performance that we cannot yet categorize clearly in any of the Performance sub-components.

We would also like to move bugs into these new components:

  • Bugs in Core::Performance with keyword perf:startup to Core::Performance: Startup (query)
  • Bugs in Core::Performance with keyword perf:responsiveness to Core::Performance: Responsiveness (query)
  • Bugs in Core::Performance with keyword perf:animation to Core::Performance: Responsiveness (query)
  • Bugs in Core::Performance with keyword perf:pageload to Core::Performance: Navigation (query)

What is the recommendation for making bulk changes like these?

Before proceeding with the changes, I would like :bas to review and confirm that these requirements are correct.

Flags: needinfo?(bas)
Assignee: nobody → dkl
Status: NEW → ASSIGNED

Oops. I will hold off until bas has a chance to look at this.

Assignee: dkl → nobody
Status: ASSIGNED → NEW

This looks good to me.

Flags: needinfo?(bas)

We're good to proceed, thanks!

Flags: needinfo?(dkl)
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Flags: needinfo?(dkl)

(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #3)

We're good to proceed, thanks!

Sorry. I will need a team name for each of the new components. Such as 'Performance Engineering', 'OS Integration', etc.

Flags: needinfo?(dave.hunt)

(In reply to David Lawrence [:dkl] from comment #4)

(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #3)

We're good to proceed, thanks!

Sorry. I will need a team name for each of the new components. Such as 'Performance Engineering', 'OS Integration', etc.

Here are the component -> team mappings:

  • Core::Performance: Startup: Performance Engineering
  • Core::Performance: Responsiveness: Performance Engineering
  • Core::Performance: Navigation: Performance Engineering
  • Core::Performance: Memory: Performance Engineering
  • Firefox::Performance: Frontend
  • Core::Performance: General: Performance Engineering
Flags: needinfo?(dave.hunt)
Flags: needinfo?(dkl)

Sorry for the time it took but this should all be done now. Let me know if anything looks incorrect.

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(dkl)
Resolution: --- → FIXED

Just to make sure you get this notification cause my email was disabled, this has now been completed.

I think the Performance: Memory component has the wrong name? It's currently Core::Core::Performance: Memory
https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Core%3A%3APerformance%3A%20Memory

(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #0)

  • Create component Core::Performance: Memory in the Core product:
    • Triage owner: Justin Link
    • Description: Issues related to excessive browser memory usage, including when the memory usage is responsible for direct performance degradation.

(In reply to Francesco Lodolo [:flod] from comment #8)

I think the Performance: Memory component has the wrong name? It's currently Core::Core::Performance: Memory
https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Core%3A%3APerformance%3A%20Memory

My bad. I cut and pasted from the original comment which had the typo in it and did not register in my mind that it was wrong. I will fix it now.

Thanks @dkl this all looks great! Apologies for the typo, and thanks for spotting it @flod!

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.