Telemetry: Remove unnessessary 'benchmark' traces.

content/browser/renderer_host/input/synthetic_gesture_target_android.cc

Index: content/browser/renderer_host/input/synthetic_gesture_target_android.cc
diff --git a/content/browser/renderer_host/input/synthetic_gesture_target_android.cc b/content/browser/renderer_host/input/synthetic_gesture_target_android.cc
index a093b4e818e9279b1df5ed6f6ea4acd2f5eaad2e..f8aeabb5d61207e0878bcad56c7a5d791d766d2f 100644
--- a/content/browser/renderer_host/input/synthetic_gesture_target_android.cc
+++ b/content/browser/renderer_host/input/synthetic_gesture_target_android.cc
@@ -32,14 +32,14 @@ bool SyntheticGestureTargetAndroid::RegisterTouchEventSynthesizer(JNIEnv* env) {
 
 void SyntheticGestureTargetAndroid::TouchSetPointer(
     JNIEnv* env, int index, int x, int y, int id) {
-  TRACE_EVENT0("benchmark", "SyntheticGestureTargetAndroid::TouchSetPointer");
+  TRACE_EVENT0("input", "SyntheticGestureTargetAndroid::TouchSetPointer");
   Java_TouchEventSynthesizer_setPointer(env, touch_event_synthesizer_.obj(),

[jdduke (slow), 2014/02/26 21:56:25]

Soon we may not have to use the TouchEventSynthesizer at all
(https://codereview.chromium.org/181833003/).  In fact, I'm not married to the
trace markers in this file at all if they haven't proved useful to the fastpath
trace scraping, i.e., if you want to get rid of them entirely go for it :)

[epennerAtGoogle, 2014/02/26 22:15:12]

Some of these did actually show as as having significant CPU time:

SyntheticGestureController::Flush	 0.5697 inclusive	 0.0407 exclusive	 1.02
calls
SyntheticGestureTarget::DispatchInputEventToPlatform	 0.5314 inclusive	 0.0354
exclusive	 1.02 calls
SyntheticGestureTargetAndroid::TouchInject	 0.4646 inclusive	 0.4619 exclusive	
1.02 calls

However for the low-noise benchmark on the bots, we want to disable all
'details'. We can still get these details locally though, so let's keep it for
now.

As a second pass, I want to disable enough 'details' such that they are all
meaningful and don't add noise to each-other, but that's for another patch.

[jdduke (slow), 2014/02/26 22:21:44]

Sounds good.

I guess the SyntheticGestureTargetAndroid::TouchInject exclusive time is such
because tracing doesn't support nested trace events when you go C++ -> Java ->
C++?   That is, TouchInject is what inserts the MotionEvent into the Java
pipeline, which in turn dispatches the event to native code for
processing/forwarding (and that portion of the native pipeline is definitely
traced).  In any case, that time looks about right for the complete touch
processing time per event.

                                       index, x, y, id);
 }
 
 void SyntheticGestureTargetAndroid::TouchInject(
     JNIEnv* env, Action action, int pointer_count, int64 time_in_ms) {
-  TRACE_EVENT0("benchmark", "SyntheticGestureTargetAndroid::TouchInject");
+  TRACE_EVENT0("input", "SyntheticGestureTargetAndroid::TouchInject");
   Java_TouchEventSynthesizer_inject(env, touch_event_synthesizer_.obj(),
                                     static_cast<int>(action), pointer_count,
                                     time_in_ms);