rpc_flight_recorder should use a finer time resolution |
||
Issue descriptionhttp://shortn/_vAjKVslv6i Almost all counts, most of the time, are ending up in the 0 to 1 seconds bucket. That makes it a pretty poor gauge of behavior when things are behaving normally-ish. We have a |scale| factor now in our distribution metrics. Let's use it.
,
Oct 7 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/e5a4c4cc16524c855750cccbf3b629794c189403 commit e5a4c4cc16524c855750cccbf3b629794c189403 Author: Aviv Keshet <akeshet@chromium.org> Date: Sat Oct 07 04:31:19 2017 autotest: rpc_flight_recorder measure in milliseconds BUG= chromium:772250 TEST=None Change-Id: I6842b4a3548aea3209a38e54944fb6506b69fc17 Reviewed-on: https://chromium-review.googlesource.com/704077 Commit-Ready: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> [modify] https://crrev.com/e5a4c4cc16524c855750cccbf3b629794c189403/site_utils/rpc_flight_recorder.py
,
Oct 9 2017
fixed, working http://shortn/_1FN0Jdvceu
,
Oct 9 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by akes...@chromium.org
, Oct 6 2017Status: Started (was: Untriaged)