cc: Track BeginMainFrame more precisely in CompositorTimingHistory.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 42330e5e123a21c856080f82647b4c8755e620c8..6e5930812d6d766fd4736618d7e70af3f9050d35 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -40658,6 +40658,35 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Scheduling.BeginMainFrameQueueDurationCritical"
+    units="microseconds">
+  <owner>brianderson@chromium.org</owner>
+  <summary>
+    How long it takes for the main side to start the BeginMainFrame in response
+    to the compositor's SendBeginMainFrame when the on_critical_path flag is not
+    set.
+  </summary>
+</histogram>
+
+<histogram name="Scheduling.BeginMainFrameQueueDurationNotCritical"
+    units="microseconds">
+  <owner>brianderson@chromium.org</owner>
+  <summary>
+    How long it takes for the main side to start the BeginMainFrame in response
+    to the compositor's SendBeginMainFrame when the on_critical_path flag is
+    set.

[Ilya Sherman, 2015/11/06 01:05:56]

nit: It seems like this histogram should be when the flag is not set, and the
one above should be when it is set -- no?

[brianderson, 2015/11/06 02:07:59]

Good eye. Done.

+  </summary>
+</histogram>
+
+<histogram name="Scheduling.BeginMainFrameStartToCommitDuration"
+    units="microseconds">
+  <owner>brianderson@chromium.org</owner>
+  <summary>
+    The time from when the main side acually starts the BeginMainFrame to when
+    the commit completes on the impl side.
+  </summary>
+</histogram>
+
 <histogram name="Scheduling.BeginMainFrameToCommitDuration"
     units="microseconds">
   <owner>brianderson@chromium.org</owner>
@@ -76689,6 +76718,15 @@ To add a new entry, add it with any value and run test to compute valid value.
   <affected-histogram name="Scheduling.PrepareTilesDuration"/>
 </histogram_suffixes>
 
+<histogram_suffixes name="CompositorTimingHistoryProcess2" separator="."
+    ordering="prefix">
+  <suffix name="Browser"/>
+  <suffix name="Renderer"/>
+  <affected-histogram name="Scheduling.BeginMainFrameQueueDurationCritical"/>
+  <affected-histogram name="Scheduling.BeginMainFrameQueueDurationNotCritical"/>
+  <affected-histogram name="Scheduling.BeginMainFrameStartToCommitDuration"/>
+</histogram_suffixes>
+
 <histogram_suffixes name="CompositorTimingHistorySubcategory" separator=".">
   <suffix name="NotUsedForEstimate"
       label="Samples that don't affect estimates. For example, because we are
@@ -76714,6 +76752,24 @@ To add a new entry, add it with any value and run test to compute valid value.
   <affected-histogram name="Scheduling.Renderer.PrepareTilesDuration"/>
 </histogram_suffixes>
 
+<histogram_suffixes name="CompositorTimingHistorySubcategory2" separator=".">
+  <suffix name="NotUsedForEstimate"
+      label="Samples that don't affect estimates. For example, because we are
+             coming out of idle."/>
+  <affected-histogram
+      name="Scheduling.Browser.BeginMainFrameQueueDurationCritical"/>
+  <affected-histogram
+      name="Scheduling.Browser.BeginMainFrameQueueDurationNotCritical"/>
+  <affected-histogram
+      name="Scheduling.Browser.BeginMainFrameStartToCommitDuration"/>
+  <affected-histogram
+      name="Scheduling.Renderer.BeginMainFrameQueueDurationCritical"/>
+  <affected-histogram
+      name="Scheduling.Renderer.BeginMainFrameQueueDurationNotCritical"/>
+  <affected-histogram
+      name="Scheduling.Renderer.BeginMainFrameStartToCommitDuration"/>
+</histogram_suffixes>
+
 <histogram_suffixes name="ConnCountImpact">
   <suffix name="conn_count_16" label="with 16 persistent connections per host"/>
   <suffix name="conn_count_4" label="with 4 persistent connections per host"/>