Add a protocol for sending FrameMetrics over IPC so we don't keep so many duplicate copies of it

NEW
Unassigned

Status

()

Core
Panning and Zooming
P3
normal
4 years ago
4 months ago

People

(Reporter: kats, Unassigned)

Tracking

({memory-footprint, perf})

Firefox Tracking Flags

(Not tracked)

Details

(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.
Keywords: perf
OS: Gonk (Firefox OS) → All
Whiteboard: gfx-noted
Keywords: footprint
(Reporter)

Updated

4 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.