diff options
| author | tonychun <tonychun@google.com> | 2015-08-12 19:52:22 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-08-13 02:52:59 +0000 |
| commit | 43fcaac5b9d6854b2fdca4335b6d1602a6b20dc8 (patch) | |
| tree | 5576d8c4c56ca58b792364aed51cf536fb69da75 /AUTHORS | |
| parent | 2fb1f4453988ad1a6e4b0851404adbd40f8c5739 (diff) | |
| download | chromium_src-43fcaac5b9d6854b2fdca4335b6d1602a6b20dc8.zip chromium_src-43fcaac5b9d6854b2fdca4335b6d1602a6b20dc8.tar.gz chromium_src-43fcaac5b9d6854b2fdca4335b6d1602a6b20dc8.tar.bz2 | |
Adding first performance measurement test to Chromoting Waterfall.
After running about 500 simulations on a swarming bot, I found that the time to authenticate and time between authenticated and connected on the Chromoting Waterfall does not exceed more than 1000 ms each (max for each is 671 ms and 646 ms, respectively). Having a 2000 ms threshold for both measurements is more than enough time to authenticate and connect.
Both Sergey and Anand have checked off on these thresholds to determine whether or not we have a bug.
BUG=
Review URL: https://codereview.chromium.org/1291533002
Cr-Commit-Position: refs/heads/master@{#343154}
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions