Closed
Bug 1066763
Opened 10 years ago
Closed 6 years ago
Add a protocol for sending FrameMetrics over IPC so we don't keep so many duplicate copies of it
Categories
(Core :: Panning and Zooming, defect, P3)
Core
Panning and Zooming
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: kats, Unassigned)
Details
(Keywords: memory-footprint, perf, Whiteboard: gfx-noted)
As of bug 967844 we can have multiple layers associated with a FrameMetrics (and multiple FrameMetrics on a layer) and since the FrameMetrics class is pretty big (and growing) it would be a nice optimization to not keep sending this data structure over the IPC channel as often.
This is something Matt suggested back in bug 967844 comment 50 but I deferred to later in the interests of getting stuff landed. However this is definitely something we should do.
Also it might be worth renaming FrameMetrics to ScrollMetrics or something, and maybe trying to carve it up into smaller classes because it gets passed around a lot, with a bunch of users only needing a few fields from it.
|
Reporter | |
Updated•9 years ago
|
|
|
Reporter | |
Updated•7 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 1•6 years ago
|
||
In the WebRender codepath we do this, by deduplicating the metrics in the WebRenderScrollData here. I'm not sure it's worth trying to implement this for the non-WebRender codepath since the plan is to transition everything to WebRender eventually.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•