Open Bug 1378418 (devtools-performance) Opened 2 years ago Updated 6 days ago

[meta] DevTools Performance improvement

Categories

(DevTools :: General, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: gl, Unassigned)

References

(Depends on 61 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

Meta bug for fixing performance issues in DevTools.
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.
Depends on: 1378964
Depends on: 1365574
Keywords: meta
Priority: -- → P3
Depends on: 1393086
Depends on: 1394804
Depends on: 1396539
Depends on: 1397745
Depends on: damp
Depends on: 1399242
Depends on: 1399909
Depends on: 1403090
Depends on: 1403894
Depends on: 1387823
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?
Flags: needinfo?(hkirschner)
Depends on: 1405581
Depends on: 1403683
Depends on: 1407988
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.
Flags: needinfo?(hkirschner) → needinfo?(spenades)
Summary: [meta] DevTools Photon - Improve performance → [meta] DevTools Performance improvement
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'.
Flags: needinfo?(spenades)
Depends on: 1410141
Depends on: 1410921
Depends on: 1411904
Depends on: 1412319
Depends on: 1410716
Depends on: 1419345
Depends on: 1403871
Depends on: 1419533
Depends on: 1421074
Depends on: 1421066
Depends on: 1423517
Depends on: 1434305
Depends on: 1453044
Depends on: 1458194
Depends on: 1458899
Depends on: 1453436
Depends on: 1439509
Depends on: 1441785
Product: Firefox → DevTools
Depends on: 1473163
Depends on: 1493179
Depends on: 1494162
Depends on: 1505254
Depends on: 1512592
Depends on: 1514915
Depends on: 1515801
Depends on: 1517198
Depends on: dbg-perf
Depends on: 1517210
Depends on: 1530822
Depends on: 1539502
Depends on: 1539518
Depends on: 1538092
Depends on: 1546513
Depends on: 1553178
No longer depends on: 1539502
No longer depends on: 1476869
No longer depends on: 1512592
No longer depends on: 1439509
Depends on: 1555498
Depends on: 1555522
Depends on: 1555377
Depends on: 1556068
Depends on: 1556620
No longer depends on: 1453436
Depends on: dt-leak
Depends on: 1557305
Depends on: 1558636
Depends on: 1565733
Depends on: 1565734
Depends on: 859371
Depends on: 1567633
Depends on: 1571349
Depends on: 1572253
Depends on: 1550108
No longer depends on: 1583070
Depends on: 1247751
You need to log in before you can comment on or make changes to this bug.