Added trace events to ResourceDispatcher to try capturing uncategorized time. This...
commitd2712ffe5161c74d458bfdeadbfee38cd6eea0dd
authorsimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 19 Oct 2013 17:54:09 +0000 (19 17:54 +0000)
committersimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 19 Oct 2013 17:54:09 +0000 (19 17:54 +0000)
tree09df16ab1211c3e5c584dab63f1e6732d66e3bb0
parent0d27cada41f19cbd0a59bcdbcfb1c23ffd0c022f
Added trace events to ResourceDispatcher to try capturing uncategorized time. This is part of an effort to identify what contributes to the ~12.6% "uncategorized" time from the android top 25k experiment.

Since we'll be re-running the experiment with tracing in the future, would like to have tracing events that cover the costlier things that DevTools timeline covers (ResourceReceivedData and ResourceReceiveResponse), as well as some other calls which accounted for ~1% of traces for sites high in "uncategorized" time.

BUG=

Review URL: https://codereview.chromium.org/26940003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229596 0039d316-1c4b-4281-b951-d872f2087c98
content/child/resource_dispatcher.cc