diff options
author | chase@chromium.org <chase@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-11 01:09:39 +0000 |
---|---|---|
committer | chase@chromium.org <chase@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-11 01:09:39 +0000 |
commit | e896a4d2af4d4c15aeeeb66fb2b18950f777f103 (patch) | |
tree | d16bfa1dbbc232298f3cbd1369b26ea00c65dba3 /net/base | |
parent | bd3dc94a54d7db7e08a3cbeacc690c6bc76ec0d8 (diff) | |
download | chromium_src-e896a4d2af4d4c15aeeeb66fb2b18950f777f103.zip chromium_src-e896a4d2af4d4c15aeeeb66fb2b18950f777f103.tar.gz chromium_src-e896a4d2af4d4c15aeeeb66fb2b18950f777f103.tar.bz2 |
Add a RWH_TabSwitchPaintDuration histogram.
The RWH_TabSwitchPaintDuration histogram calculates
the amount of time it took after a particular view was
selected for it to be fully painted.
I modified the tab switching test to use the new tab
switch paint duration histogram in place of the whiteout
duration histogram. As a measure, whiteout duration
would not carry a value if we kept the backing store
around for a tab, and we would end up with a result of
zero instead of a useful result. Local results with the
new measure are consistent with the number of operations
we perform on the tabs.
The tab switching test now fails if it cannot locate
the correct histogram.
BUG=4104
TEST=count of tab switch paint duration histogram
results in tab switching test equals number of tabs
used in test
Review URL: http://codereview.chromium.org/378038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31632 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base')
0 files changed, 0 insertions, 0 deletions