Add runs/ms to perf dashboard unit info.

Add runs/ms to perf dashboard unit info.

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

[tonyg, 2014-01-05 20:10:13]

https://codereview.chromium.org/119473003/diff/1/tools/perf/unit-info.json
File tools/perf/unit-info.json (right):

https://codereview.chromium.org/119473003/diff/1/tools/perf/unit-info.json#ne...
tools/perf/unit-info.json:84: "runs/ms": {
This is fine, but I'd just like to check first whether it might make sense to
change the test to report runs/s instead of adding a new unit. If this number
goes fractional, it might start to interfere with our ability to catch
regressions (I think we assume no test needs more than 2 decimal places or
something).

[rileya (GONE FROM CHROMIUM), 2014-01-07 18:54:28]

On 2014/01/05 20:10:13, tonyg wrote:
> https://codereview.chromium.org/119473003/diff/1/tools/perf/unit-info.json
> File tools/perf/unit-info.json (right):
> 
>
https://codereview.chromium.org/119473003/diff/1/tools/perf/unit-info.json#ne...
> tools/perf/unit-info.json:84: "runs/ms": {
> This is fine, but I'd just like to check first whether it might make sense to
> change the test to report runs/s instead of adding a new unit. If this number
> goes fractional, it might start to interfere with our ability to catch
> regressions (I think we assume no test needs more than 2 decimal places or
> something).

The tests in question (vector math microbenchmarks) were producing huge 500,000
to > 1,000,000 runs/s numbers. Even the unoptimized paths for the slowest of the
android bots get at least 100 runs/ms, so I don't see things going fractional
for the current crop of tests using runs/ms.

[tonyg, 2014-01-07 18:58:00]

lgtm

[commit-bot: I haz the power, 2014-01-07 19:04:04]

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

[commit-bot: I haz the power, 2014-01-07 22:16:43]

Change committed as 243404