Issue 646319 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	samans@chromium.org
Closed:	Nov 2016
Cc:	danakj@chromium.org rjkroege@chromium.org sadrul@chromium.org piman@chromium.org sky@chromium.org mustash-bugs@google.com
Components:	Internals>Compositing>Quads
EstimatedDays:	----
NextAction:	----
OS:	All , Chrome
Pri:	3
Type:	Bug
Proj-Mustash Proj-Mustash-Chrome Proj-Mustash-Mus-GPU VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Mus+Ash: Measure cost of CompositorFrame IPCs from ui::Compositor

Project Member Reported by fsam...@chromium.org, Sep 13 2016

Issue description

Today, ui::Compositor submits CompositorFrames directly to SurfaceFactory without IPC. In Mus+Ash, we require this to be an IPC boundary because SurfaceFactory and the display compositor live in the Mus-Gpu process. Ideally, we should unify code paths between Chrome and Mus+Ash but this means doing IPC in ui::Compositor where we previous had none.

As such, we need to measure the cost of doing this.

Comment 1 by dtapu...@chromium.org, Sep 13 2016

Components: MUS

Comment 2 by rjkroege@chromium.org, Sep 13 2016

Components: -MUS Internals>Compositing
Labels: Proj-Mustash-Mus-GPU

Comment 3 by fsam...@chromium.org, Sep 13 2016

Cc: -vollick@chromium.org danakj@chromium.org

+danakj@ we need to do this for Mus+Ash so it would be nice to optionally measure the cost of CompositorFrame IPCs within the ui::Compositor to the display compositor just to understand what impact has independent from the rest of Mus+Ash.