Open
Bug 1706359
Opened 4 years ago
Updated 3 years ago
Investigate and improve inspector selector search performance
Categories
(DevTools :: Inspector, enhancement)
DevTools
Inspector
Tracking
(Fission Milestone:Future)
NEW
Fission Milestone | Future |
People
(Reporter: bomsy, Unassigned)
References
(Blocks 2 open bugs)
Details
Once Bug 1568880 lands, this should fix inspector selector searching over a top-level document and its sub-frames, as part of the fission work. The findNextNode
inspector command currently fetches all search results (as a node list) of each of the inspector fronts even though only one node is returned to the front-end on each call. There is a potential for perf issues if there lots of results.
We should investigate (get a profile and some perf numbers) and see the possibility of not having to fetch the whole result set each time.
Reporter | ||
Updated•4 years ago
|
Blocks: dt-fission-perf
Reporter | ||
Updated•4 years ago
|
Blocks: meta-inspector-search
Updated•3 years ago
|
Fission Milestone: --- → Future
You need to log in
before you can comment on or make changes to this bug.
Description
•