diff options
author | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-23 00:52:13 +0000 |
---|---|---|
committer | rlarocque@chromium.org <rlarocque@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-23 00:52:13 +0000 |
commit | ffe38f8add90e8c29055cd2aed4937ed5c45273a (patch) | |
tree | 2e15768f0ca577d9efe2512ecbf6a66d533169ba /content/browser/tab_contents/tab_contents.h | |
parent | ebc335f384af41ec5b919588a9217253073dc299 (diff) | |
download | chromium_src-ffe38f8add90e8c29055cd2aed4937ed5c45273a.zip chromium_src-ffe38f8add90e8c29055cd2aed4937ed5c45273a.tar.gz chromium_src-ffe38f8add90e8c29055cd2aed4937ed5c45273a.tar.bz2 |
Event tracing for sync events
Adds a "sync" trace event category that traces the following events:
- model association time
- time spent in each step of the syncer state machine
- transactions
Also included is a "sync_lock_contention" category that tracks the time spent
acquiring the sync lock. This information would normally clutter up the logs,
but it is useful information when we suspect lock contention is an issue.
To trace model association tracing, I needed to have a set of strings with
application lifetime representing each model type. I have changed the
return type of ModelTypeToString from std::string to const char* to meet this
need.
In the interest of avoiding duplicate functionality, this change also removes
other mechanisms for tracing transaction time. In particular, some of the log
messages around acquiring and releasing transactions have been removed.
BUG=104353
TEST=Run with '--trace-startup=sync,sync_lock_contention', open resulting
chrometrace.log in about:tracing.
Review URL: http://codereview.chromium.org/8573011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111265 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/tab_contents/tab_contents.h')
0 files changed, 0 insertions, 0 deletions