diff options
author | ernstm@chromium.org <ernstm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-28 20:18:45 +0000 |
---|---|---|
committer | ernstm@chromium.org <ernstm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-28 20:18:45 +0000 |
commit | bbb26915eae6ccf279877e8f7f033a73b551f757 (patch) | |
tree | 97a5cf8c8cc3c453b27da665cbfd08a190cabd92 /content/shell/browser | |
parent | 625b131416a73c3381c4ad663121fadc34e03876 (diff) | |
download | chromium_src-bbb26915eae6ccf279877e8f7f033a73b551f757.zip chromium_src-bbb26915eae6ccf279877e8f7f033a73b551f757.tar.gz chromium_src-bbb26915eae6ccf279877e8f7f033a73b551f757.tar.bz2 |
re-land: Use browser compositor rendering stats in smoothness
PERF SHERRIFS: This patch can change the metrics of smoothness up or down.
The new values should be more accurate than what we had before. If there are
large changes on a platform, we should still sanity check that everything works
as expected.
Switch smoothness benchmark to use rendering stats from the top level
compositor; i.e. if data from a browser compositor is available, use that.
Otherwise use the data from the renderer compositor.
The re-land fixes the problem where a browser compositor was present, but
didn't record rendering stats. That was the case with the reference
builds (that didn't have the patch that enabled recording) and on Android.
The new version checks if the browser compositor rendering stats events
actually have frames in them. If not, the render compositor stats will be used.
There is also a fix on the way to enable the recording on Android
(https://codereview.chromium.org/168193004/).
R=tonyg@chromium.org,nduca@chromium.org
BUG=340753
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=254811
Review URL: https://codereview.chromium.org/174663008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260256 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/shell/browser')
0 files changed, 0 insertions, 0 deletions