Adjust Task Latency Histograms to Microseconds |
||
Issue descriptionWhen checking the histograms, it seemed that milliseconds was too long of a time period for task latency to get any good data. Switching this to microseconds may reveal more interesting groupings for task latency.
,
Apr 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/180f23bbfdd91ade1b232094a17e48a4e590f38d commit 180f23bbfdd91ade1b232094a17e48a4e590f38d Author: robliao <robliao@chromium.org> Date: Fri Apr 28 21:34:13 2017 Record the TaskLatency Histogram in Microseconds Instead of Milliseconds Most task latencies were between 0 and 1 ms. Recording task latencies in microseconds will provide better data BUG= 715777 Review-Url: https://codereview.chromium.org/2839333002 Cr-Commit-Position: refs/heads/master@{#468135} [modify] https://crrev.com/180f23bbfdd91ade1b232094a17e48a4e590f38d/base/task_scheduler/task_tracker.cc [modify] https://crrev.com/180f23bbfdd91ade1b232094a17e48a4e590f38d/base/task_scheduler/task_tracker_unittest.cc [modify] https://crrev.com/180f23bbfdd91ade1b232094a17e48a4e590f38d/tools/metrics/histograms/histograms.xml
,
Jul 6 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by gab@chromium.org
, Apr 27 2017