DescriptionReport 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.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274390
Patch Set 1 #Patch Set 2 : better formatting #Patch Set 3 : also search latency slice in renderer process since that's where plugin input event's latency is ge… #
Messages
Total messages: 5 (0 generated)
|