Open Bug 1527150 Opened 5 years ago Updated 2 years ago

Investigate nsIFrame memory layout, and how useful it is for display list building

Categories

(Core :: Web Painting, enhancement, P4)

Product:
Core
Component:
Web Painting
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox67 --- affected

People

(Reporter: mattwoodrow, Unassigned)

References

(Blocks 1 open bug)

Details

Display list building iterates large chunks of the frame tree, and is almost entirely memory bandwidth bound.

It would be interesting to investigate how the frame constructor arranges frames in memory, and if this is the same order as we iterate for display list building (and other algorithms that access frames a lot, like reflow).

It is possible that changing the order to increase the likelihood of us being able to progress sequentially through memory will also increase DL building performance.

Priority: -- → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.