GitLab

In a recent refactoring we opted to switch to microseconds because
that's TimeDelta's finest resolution but results are now 0 or 1 us
always and it makes the dashboard useless.

I think it's okay to yield results in nanoseconds because it's an
effective average of 0-1 us samples.

The common perf test solution to this is to measure a batch of, e.g.,
1000 calls but this is tricky with WaitableEvent because we want to
measure Signal/Wait() from multiple threads but not the dead time in
between.

R=kylechar@chromium.org, skyostil@chromium.org

Bug: 905412
Change-Id: I30daf41535d36ff59b19a64523f0a558c3fa1b2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724699
Commit-Queue: Gabriel Charette <gab@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Auto-Submit: Gabriel Charette <gab@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#681871}