diff options
author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-15 15:13:52 +0000 |
---|---|---|
committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-15 15:13:52 +0000 |
commit | 05c8e50113e840b25745125dea309e50ddb5d800 (patch) | |
tree | 8c316525c3ee3f5bcfbbf3c6de1a592adfc211ef /base/values.h | |
parent | bff1f51a7aa9c3dd72711304b5f0f158de74d630 (diff) | |
download | chromium_src-05c8e50113e840b25745125dea309e50ddb5d800.zip chromium_src-05c8e50113e840b25745125dea309e50ddb5d800.tar.gz chromium_src-05c8e50113e840b25745125dea309e50ddb5d800.tar.bz2 |
Clean up PLT histograms for a move to navigator_state.cc
Clean up PLT gathering in preparation for moving it
to take place in navigation_state.cc, during the
instance destructor. This CL should have almost
no semantic impact, and I'm submitting it separately
so that when I move large blocks, I can mostly move
them unchanged.
Add a bunch of DCHECKs to be sure that finish and finish_doc
times are only set once, and that they are set only in
the correct order.
In a future CL, I expect to push a lot of the time-gathering
code into navigation_state.cc, along with the generation
of the final histograms. The challenge is to mark the
NavigationState instances that are worthy of recording
(which looks like it MAY be done by marking the state
with the boolean to indicate it is part of an HTTP or
HTTPS connection), and make sure we have good numbers
throughout.
bug=48970
r=mbelshe
Review URL: http://codereview.chromium.org/2993004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56164 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/values.h')
0 files changed, 0 insertions, 0 deletions