New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 653132 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 578176



Sign in to add a comment

Estimated Queuing Time for compositor thread

Project Member Reported by dproy@chromium.org, Oct 5 2016

Issue description

Current implementations of Estimated Input Latency only takes into account tasks on the main thread. We can improve this estimate by incorporating estimated task queuing time on the compositor thread.

The feasibility of this metric will depend on: 

- Can we easily instrument all tasks?
- Will measuring task duration be too costly?

 

Comment 1 by dproy@chromium.org, Oct 5 2016

Labels: -Type-Bug Type-Feature
Components: Speed>Metrics
Cc: alexclarke@chromium.org
Status: Assigned (was: Untriaged)
Alex, do we have a bug for getting a scheduler on the renderer compositor thread? This should be blocked on that, I think.
Blockedon: 578176
This is the closest thing we've got.  https://bugs.chromium.org/p/chromium/issues/detail?id=578176
Cc: ojan@chromium.org altimin@chromium.org
Labels: -Pri-1 Pri-3
Status: Available (was: Assigned)
Bumping down to Pri-3.

We don't have any concrete plans for this in Q4.
Cc: dproy@chromium.org
Owner: ----

Comment 7 by npm@chromium.org, Jan 12 2018

Cc: npm@chromium.org

Comment 8 by dproy@chromium.org, Mar 16 2018

Labels: -progressivewebmetrics

Sign in to add a comment