1378418 - (devtools-performance) [meta] DevTools Performance improvement

Status: NEW

(DevTools :: General, enhancement, P3)

Description

[Gabriel Luong [:gl] (ΦωΦ)]

Meta bug for fixing performance issues in DevTools.

Comment 1

[Andrei Petcu]

I think #1311616, #1125322 and #1176050 might be duplicates of the same bug. I'm not 100% sure.

People are using the network monitor to see "how fast Firefox loads pages". The result is that they get the impression that Firefox loads them slowly when in fact the Network Monitor is slowing down the page loads. I saw a recent benchmark on youtube mistakenly making this statement.

Comment 2

[Alexandre Poirot [:ochameau]]

Should we use this bug as meta bug for "Quantum flow for DevTools" and rename it accordingly?
This bug is the overall meta bug for any performance issue on devtools.
Would Quantum flow for devtools require a more focused scope?

Comment 3

[:Harald Kirschner :digitarald]

Renamed the bug as photon was mostly the redesign.

:sole, as you are thinking about triaging and bug tracking; should we keep the meta bug tracker or should we use whiteboard tags to mark bugs as part of flow. Using flexible whiteboard tags that focused on prioritizing issues within the flow program helped Quantum Flow as a cross-functional effort.

Comment 4

[Soledad Penades [:sole] [:spenades]]

Perhaps we want to use the parent bug 1378416 ... which is also "Photon", but seems to be about performance as well?

Looking at the tree view I can see lots of unprioritised bugs:
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1378416&hide_resolved=1

It would be hard to decide what to work on just by looking at this. So yes, we need to use 'something' like the whiteboard tags. Or simply the "Importance" field? What's stopping us from using it?

We should take this list of bugs and reprioritise to follow the plan we discussed in the doc. We might also be missing bugs here, I would expect each team panel to fill in these gaps once we start working more heavily on this (we're meeting tomorrow morning).

I'm happy to go through the list of bugs and massively prioritise once we have that meeting and everyone is 'on the same page'.