Open
Bug 1476154
Opened 6 years ago
Updated 2 years ago
Investigate performance improvements for the frame constructor
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
NEW
People
(Reporter: bholley, Unassigned)
References
(Depends on 4 open bugs, Blocks 1 open bug)
Details
(Keywords: perf, Whiteboard: [layout:backlog:quality])
This is a placeholder bug for investigation that the layout performance folks will want to do at some point.
The frame constructor is a beast of a component, and a lot of inefficiency lurks behind its complexity. There are four basic areas I can think of where we may be able to improve things:
* Being more precise about change hint handling to avoid unnecessary reconstructs.
* Doing a better job of handling dynamic insertions and removals to avoid unnecessary (or overly-broad) reconstructs.
* Simplifying or micro-optimizing the core algorithms, to either do less work or do it faster.
The first two only apply to dynamic change handling, which is generally an area where our regression tests aren't great, so there may be some pretty dumb stuff there. The last one applies across the board.
Updated•5 years ago
|
Whiteboard: [layout:backlog:code-quality]
Updated•5 years ago
|
Whiteboard: [layout:backlog:code-quality] → layout:backlog:quality
Updated•5 years ago
|
Whiteboard: layout:backlog:quality → [layout:backlog:quality]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•