Adding chrome_inputs_per_frame.sql to track input count per frame
This metric tracks the number of inputs per frame, as inputs get
coalesced if the previous frame processing in the renderer hasn't
finished yet, this is a good metric to track scroll jank as the
more user input events per frame there is, the jankier the scroll.
Bug:239406313
Change-Id: I0d77c8f4f399f9d6767b6d273e08cff9c4c61d51
diff --git a/Android.bp b/Android.bp
index c45934a..af826ce 100644
--- a/Android.bp
+++ b/Android.bp
@@ -9046,6 +9046,7 @@
"src/trace_processor/metrics/sql/chrome/chrome_input_to_browser_intervals.sql",
"src/trace_processor/metrics/sql/chrome/chrome_performance_mark_hashes.sql",
"src/trace_processor/metrics/sql/chrome/chrome_processes.sql",
+ "src/trace_processor/metrics/sql/chrome/chrome_scroll_inputs_per_frame.sql",
"src/trace_processor/metrics/sql/chrome/chrome_scroll_jank_caused_by_scheduling.sql",
"src/trace_processor/metrics/sql/chrome/chrome_slice_names.sql",
"src/trace_processor/metrics/sql/chrome/chrome_stack_samples_for_task.sql",
