The data for these graphs was gathered from real-world trace collected during regular use on Android. The graphs show what the main thread of the renderer is doing during a given input latency event. The duration of an input latency event starts when that event is dispatched from the browser to the renderer and ends when a frame is committed as a result of the input event. All data is from traces that took longer than 100ms.
Queuing time is the time from when the event is dispatched to the renderer to when the renderer begins to handle the event.
Handling time is the time from when the renderer begins to handle the event to the associated main frame commit.
Input latency trace event visualization:
There are two graphs per latency event. Trace events are represented as a stack; if 'event a' calls 'event b', 'event a' is the parent to 'event b' and 'event b' is shown under 'event a'. One graph shows the bottom layer of the events, 'Bottom-Up', and the other graph shows the top layer of events, 'Top-Down'. This gives a view of what the renderer is doing underneath as well as on the surface level.
GestureScrollBegin Data | GestureScrollUpdate Data | GestureTap Data | TouchStart Data | TouchEnd Data | TouchMove Data