Track input latency while starting a ServiceWorker for a navigation hint.

content/browser/renderer_host/input/render_widget_host_latency_tracker.cc

Index: content/browser/renderer_host/input/render_widget_host_latency_tracker.cc
diff --git a/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc b/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc
index 2b572532e517242b8ee4f23fc17e4f98fe16515d..266aaa25d3fe0e6af17f2fcf812190f986e0d318 100644
--- a/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc
+++ b/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc
@@ -96,7 +96,8 @@ void ComputeScrollLatencyHistograms(
     const LatencyInfo::LatencyComponent& gpu_swap_begin_component,
     const LatencyInfo::LatencyComponent& gpu_swap_end_component,
     int64_t latency_component_id,
-    const LatencyInfo& latency) {
+    const LatencyInfo& latency,
+    bool is_running_navigation_hint_task) {
   DCHECK(!latency.coalesced());
   if (latency.coalesced())
     return;
@@ -115,6 +116,14 @@ void ComputeScrollLatencyHistograms(
           "Event.Latency.TouchToFirstScrollUpdateSwapBegin",
           original_component, gpu_swap_begin_component);
     }
+    if (is_running_navigation_hint_task) {
+      for (size_t i = 0; i < original_component.event_count; i++) {
+        UMA_HISTOGRAM_TOUCH_TO_SCROLL_LATENCY(
+            "Event.Latency.TouchToFirstScrollUpdateSwapBegin."

[shimazu, 2016/08/16 09:46:21]

According the top of histograms.xml, I thought "...SwapBegin_" is better here
instead of "...SwapBegin.", but the unittest works... Is there difference
between the two?

https://cs.chromium.org/chromium/src/tools/metrics/histograms/histograms.xml?...

[horo, 2016/08/16 12:31:43]

I don't know well about the regulations of what separator should be used.
But "_" is a default value.
So I should probably use "_".

I uploaded Patch Set 3.

+            "IsRunningNavigationHintTask",
+            original_component, gpu_swap_begin_component);
+      }
+    }
   } else if (!latency.FindLatency(
                  ui::INPUT_EVENT_LATENCY_SCROLL_UPDATE_ORIGINAL_COMPONENT,
                  latency_component_id, &original_component)) {
@@ -128,6 +137,14 @@ void ComputeScrollLatencyHistograms(
         "Event.Latency.TouchToScrollUpdateSwapBegin", original_component,
         gpu_swap_begin_component);
   }
+  if (is_running_navigation_hint_task) {
+    for (size_t i = 0; i < original_component.event_count; i++) {
+      UMA_HISTOGRAM_TOUCH_TO_SCROLL_LATENCY(
+          "Event.Latency.TouchToScrollUpdateSwapBegin."
+          "IsRunningNavigationHintTask",
+          original_component, gpu_swap_begin_component);
+    }
+  }
 
   // TODO(miletus): Add validation for making sure the following components
   // are present and their event times are legit.
@@ -531,7 +548,8 @@ void RenderWidgetHostLatencyTracker::OnSwapCompositorFrame(
 }
 
 void RenderWidgetHostLatencyTracker::OnFrameSwapped(
-    const LatencyInfo& latency) {
+    const LatencyInfo& latency,
+    bool is_running_navigation_hint_task) {
   // Don't report frame latency on wheel events. Previously they were only
   // reported on touch metrics and we need to be consistent across reporting
   // metrics.
@@ -572,7 +590,7 @@ void RenderWidgetHostLatencyTracker::OnFrameSwapped(
 
   ComputeScrollLatencyHistograms(gpu_swap_begin_component,
                                  gpu_swap_end_component, latency_component_id_,
-                                 latency);
+                                 latency, is_running_navigation_hint_task);
 }
 
 }  // namespace content