Open
Bug 1378418
(devtools-performance)
Opened 8 years ago
Updated 3 months ago
[meta] DevTools Performance improvement
Categories
(DevTools :: General, task, P3)
DevTools
General
Tracking
(Not tracked)
NEW
People
(Reporter: gl, Unassigned)
References
(Depends on 62 open bugs)
Details
(Keywords: meta)
Meta bug for fixing performance issues in DevTools.
Reporter | ||
Updated•8 years ago
|
Blocks: devtools-photon
Depends on: 1378729
Depends on: 1378730
Depends on: 1378731
Depends on: 1378733
Depends on: 1378734
Depends on: 1378735
Depends on: 1378739
Depends on: 1378741
Depends on: 1378742
Depends on: 1378751
Depends on: 1366693
Depends on: 1289203
Depends on: 1366989
Depends on: 1358054
Depends on: 1356536
Depends on: 1350969
Depends on: 1350227
Depends on: 1349198
Depends on: 1308695
Depends on: 1308441
Depends on: 1176050
Depends on: 1353548
Depends on: 1311616
Depends on: 1302159
Depends on: dt-open-slow
Depends on: 1092821
Comment 1•8 years ago
|
||
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: 1381416
Depends on: 1381418
Depends on: 1390091
Depends on: 1390092
Depends on: 1390093
Depends on: 1390094
Depends on: 1390096
Depends on: 1390098
Depends on: 1393515
Comment 2•7 years ago
|
||
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)
Comment 3•7 years ago
|
||
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
Comment 4•7 years ago
|
||
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)
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Depends on: net-ws-perf
Updated•5 years ago
|
No longer depends on: net-ws-perf
Updated•5 years ago
|
Depends on: netmonitor-perf
Updated•5 years ago
|
Depends on: console-perf
Updated•5 years ago
|
Depends on: dt-perf-layout
Updated•4 years ago
|
Depends on: inspector-perf
Updated•4 years ago
|
Depends on: dt-fission-perf
Updated•2 years ago
|
Severity: normal → S3
Updated•9 months ago
|
Type: enhancement → task
Updated•9 months ago
|
No longer blocks: devtools-photon
You need to log in
before you can comment on or make changes to this bug.
Description
•