Use tracing data for measuring tab_switching latency |
|||
Issue descriptionThe tab_switching benchmark currently reads the UMA data for measuring the tab_switching latency. In a telemetry test, this does not produce enough data for diagnostic purposes (because of how the data is put into buckets). Using tracing data on the other hand allows collecting all the raw data, which is more useful when diagnosing a regression.
,
Jan 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/77f76c7463d5df234647e842a0ee421e35410b2a commit 77f76c7463d5df234647e842a0ee421e35410b2a Author: Sadrul Habib Chowdhury <sadrul@chromium.org> Date: Thu Jan 18 01:45:54 2018 tab_switching: Add tracing to measure tab-switching latency. Add tracing data for tab-switching latency. Include that tracing data in the tab_switching telemetry report as 'tab_switch_to_paint'. The current data collected from histogram is also included in the report. BUG=802106 Change-Id: I2e5fbb50ee36b2d93f66637dd1601865cbd1553d Reviewed-on: https://chromium-review.googlesource.com/826184 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by: Timothy Dresser <tdresser@chromium.org> Cr-Commit-Position: refs/heads/master@{#530007} [modify] https://crrev.com/77f76c7463d5df234647e842a0ee421e35410b2a/content/browser/renderer_host/render_widget_host_view_aura.cc [modify] https://crrev.com/77f76c7463d5df234647e842a0ee421e35410b2a/content/browser/renderer_host/render_widget_host_view_aura.h [modify] https://crrev.com/77f76c7463d5df234647e842a0ee421e35410b2a/content/browser/renderer_host/render_widget_host_view_mac.h [modify] https://crrev.com/77f76c7463d5df234647e842a0ee421e35410b2a/content/browser/renderer_host/render_widget_host_view_mac.mm [modify] https://crrev.com/77f76c7463d5df234647e842a0ee421e35410b2a/ui/latency/latency_tracker.cc
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
|
|||
►
Sign in to add a comment |
|||
Comment 1 by nedngu...@google.com
, Jan 16 2018