Report time-related media metrics milliseconds instead of seconds.

Report time-related media metrics in milliseconds instead of seconds.





BUG=282679
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=221256

[anandc, 2013-09-03 21:15:01]

shadi@/dtu@/tonyg@: PTAL.

This CL changes the unit of time-related media metrics from seconds to
milli-seconds. This is to help improve the situation with too-sensitive GASP
alerts for certain metrics.

[dtu, 2013-09-03 21:29:38]

Does the dashboard/GASP only support integers? Is that something we should fix?

[anandc, 2013-09-04 00:31:43]

On 2013/09/03 21:29:38, Dave Tu wrote:
> Does the dashboard/GASP only support integers? Is that something we should
fix?

Both the perf-dashboard and GASP work with floating point numbers. See here for
example:
https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=linux-release...
Notice non-integer floating point values along the Y-axis.

[dtu, 2013-09-04 00:44:58]

On 2013/09/04 00:31:43, anandc wrote:
> On 2013/09/03 21:29:38, Dave Tu wrote:
> > Does the dashboard/GASP only support integers? Is that something we should
> fix?
> 
> Both the perf-dashboard and GASP work with floating point numbers. See here
for
> example:
>
https://chromeperf.appspot.com/report?masters=ChromiumPerf&bots=linux-release...
> Notice non-integer floating point values along the Y-axis.

I don't think this will fix the bug as written (I commented on the bug), but
lgtm anyway, because milliseconds seems like a more reasonable unit for what
we're measuring here.

[sullivan, 2013-09-04 14:26:23]

On 2013/09/03 21:15:01, anandc wrote:
> shadi@/dtu@/tonyg@: PTAL.
> 
> This CL changes the unit of time-related media metrics from seconds to
> milli-seconds. This is to help improve the situation with too-sensitive GASP
> alerts for certain metrics.

Why not just change the GASP configs to be less sensitive?

[anandc, 2013-09-04 15:04:40]

On 2013/09/04 14:26:23, sullivan wrote:
> On 2013/09/03 21:15:01, anandc wrote:
> > shadi@/dtu@/tonyg@: PTAL.
> > 
> > This CL changes the unit of time-related media metrics from seconds to
> > milli-seconds. This is to help improve the situation with too-sensitive GASP
> > alerts for certain metrics.
> 
> Why not just change the GASP configs to be less sensitive?

Sure, I'll look at that. Let's see how things look with this CL. 

Reporting time in milliseconds matches our earlier PyAuto tests as well, so
committing this in now. Thanks.

[commit-bot: I haz the power, 2013-09-04 16:38:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/anandc@chromium.org/23893004/1

[commit-bot: I haz the power, 2013-09-04 20:33:18]

Change committed as 221256