Report only one input latency metric mean_input_event_latency
As telemetry result is mainly meant for monitoring regression, exposing different types of input latency, e.g. scroll/mouse/touch latency as we currently do, does not add more benefit to this purpose but instead adds more confusion for people when they look at the different input latency metrics. Lets only report one input latency metric mean_input_event_latency, which is derived from all input events which have event creation timestamp and swap buffer timestamp, regardless of its event type. BUG=378027 TEST=run telemetry smoothness tests and see only one mean_input_event_latency is reported. unittests pass. Review URL: https://codereview.chromium.org/300273002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@274390 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment