New issue
Advanced search Search tips

Issue 807464 link

Starred by 1 user
Status: Assigned
Owner:
charliea@chromium.org
Cc:
sadrul@chromium.org
chiniforooshan@chromium.org
tdres...@chromium.org
yiyix@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 790761



Sign in to add a comment

Investigate how to aggregate frame metrics across sources.

Project Member Reported by briander...@chromium.org, Jan 30 2018 
Should we:
1) Take the worst source per frame.
2) Accumulate across all sources.
3) Average across all sources.
4) Weigh sources based on context like priority of source or use cases.

Comment 1 by tdres...@chromium.org, Jan 31 2018 

I vote a combination of 1 & 4, where we prioritize sources responding to input, and use the worst source to break ties.

(As described here: https://docs.google.com/document/d/1Bot91txCWZUstt32_BBLo-_HUsvOVn_L5yaI5xre2M0/edit)

Comment 2 by maxlg@chromium.org, May 16 2018 

ping - any update?

Comment 3 by briander...@chromium.org, Jun 27 2018

Cc: yiyix@chromium.org chiniforooshan@chromium.org
Components: Internals>GPU>Metrics
Owner: ----
Status: Available (was: Assigned)

Comment 4 by npm@chromium.org, Nov 26 

This bug is stale. Is someone interested in picking this up? If there is no longer interest in these metrics then this can be closed.

Comment 5 by tdres...@chromium.org, Nov 27

Owner: charliea@chromium.org
Status: Assigned (was: Available)
This is part of the frame throughput work which is on Charlie's backlog.
►

Sign in to add a comment