SyncFS v2: Add modest logging for ApplyLocalChange, ApplyRemoteChange

BUG=240165
TEST=manual
R=nhiroki@chromium.org, tzik@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238294 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 238294
Resident set size (RSS) of multiple processes without double-counts on Linux.

It fixes logging and in-process duplication counting in tools/linux/procfs.py
at the same time.

BUG=324194
TEST=None
NOTRY=True

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238295 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 238295
Clean up outdated UMA stats for Chrome OS Google Drive integration.

- Mark Drive.EntryKind and Drive.FileFormat as obsolete. It's removed in r161277.
- Mark Drive.CacheDBOpenStatus as obsolete. It's removed in r219236.

- Mark Drive.InitialFeedLoadTime obsolete and introduce Drive.DirectoryFeedLoadTime.
  The metric is originally meant to measure the duration until
  we fetch partial result for showing quick UI response to the user.
  In the latest codebase, InitialFeedLoadTime no more is the point
  to trigger such role. Rather, DirectoryFeedLoadTime is.

- Use UMA_HISTOGRAM_LONG_TIMES for Drive.EntireFeedLoadTime and rename it
  to Drive.FullFeedLoadTime.
  It frequently goes beyond 10 seconds upperbound of UMA_HISTOGRAM_TIMES.
  (Despite the comment removed by this CL, I believe the location where
  this stat is taken is correct. The code survived several refactorings
  and at some point in history it was inappropriate...)

BUG=229407
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238296 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 238296