Delete flaky metrics from the browser perf tests.

Delete flaky metrics from the browser perf tests.

These metrics suffer from that they count the number of bytes since
the beginning of the call, and average them during the 10-second
measuring window after 60-seconds of warmup. This means that if there's
any variance in the warmup period or the call gets established a little
earlier or later, it will have a big impact on the numbers.

I think we can just delete them. An alternative approach is to
do like in https://codereview.chromium.org/2545553003 and subtract the
count at the beginning of the measuring window, which means we
effectively measure the bitrate during the measuring window. That's
covered by the test added in that patch though, only it's going through
the new stats API instead of the old one.So, let's just delete them
from the old API for now.

BUG=666725
CC=ehmaldonado@chromium.org
R=kjellander@chromium.org

Committed: https://crrev.com/054f7b1e4a7b3bbf8b1effb31ae4620918fe8787
Cr-Commit-Position: refs/heads/master@{#438474}

[kjellander_chromium, 2016-12-14 07:24:24]

lgtm

[phoglund_chromium, 2016-12-14 09:02:21]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2016-12-14 09:02:41]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-14 09:48:27]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481706141907320, "parent_rev":
"6bb8dbe357649002198a29bf4c417899a38d526b", "commit_rev":
"e3948b9854ad384ff4e726b626903845fabc0f37"}

[commit-bot: I haz the power, 2016-12-14 09:48:55]

Description was changed from

==========
Delete flaky metrics from the browser perf tests.

These metrics suffer from that they count the number of bytes since
the beginning of the call, and average them during the 10-second
measuring window after 60-seconds of warmup. This means that if there's
any variance in the warmup period or the call gets established a little
earlier or later, it will have a big impact on the numbers.

I think we can just delete them. An alternative approach is to
do like in https://codereview.chromium.org/2545553003 and subtract the
count at the beginning of the measuring window, which means we
effectively measure the bitrate during the measuring window. That's
covered by the test added in that patch though, only it's going through
the new stats API instead of the old one.So, let's just delete them
from the old API for now.

BUG=666725
CC=ehmaldonado@chromium.org
R=kjellander@chromium.org
==========

to

==========
Delete flaky metrics from the browser perf tests.

These metrics suffer from that they count the number of bytes since
the beginning of the call, and average them during the 10-second
measuring window after 60-seconds of warmup. This means that if there's
any variance in the warmup period or the call gets established a little
earlier or later, it will have a big impact on the numbers.

I think we can just delete them. An alternative approach is to
do like in https://codereview.chromium.org/2545553003 and subtract the
count at the beginning of the measuring window, which means we
effectively measure the bitrate during the measuring window. That's
covered by the test added in that patch though, only it's going through
the new stats API instead of the old one.So, let's just delete them
from the old API for now.

BUG=666725
CC=ehmaldonado@chromium.org
R=kjellander@chromium.org

Review-Url: https://codereview.chromium.org/2568133006
==========

[commit-bot: I haz the power, 2016-12-14 09:48:56]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-14 09:50:39]

Description was changed from

==========
Delete flaky metrics from the browser perf tests.

These metrics suffer from that they count the number of bytes since
the beginning of the call, and average them during the 10-second
measuring window after 60-seconds of warmup. This means that if there's
any variance in the warmup period or the call gets established a little
earlier or later, it will have a big impact on the numbers.

I think we can just delete them. An alternative approach is to
do like in https://codereview.chromium.org/2545553003 and subtract the
count at the beginning of the measuring window, which means we
effectively measure the bitrate during the measuring window. That's
covered by the test added in that patch though, only it's going through
the new stats API instead of the old one.So, let's just delete them
from the old API for now.

BUG=666725
CC=ehmaldonado@chromium.org
R=kjellander@chromium.org

Review-Url: https://codereview.chromium.org/2568133006
==========

to

==========
Delete flaky metrics from the browser perf tests.

These metrics suffer from that they count the number of bytes since
the beginning of the call, and average them during the 10-second
measuring window after 60-seconds of warmup. This means that if there's
any variance in the warmup period or the call gets established a little
earlier or later, it will have a big impact on the numbers.

I think we can just delete them. An alternative approach is to
do like in https://codereview.chromium.org/2545553003 and subtract the
count at the beginning of the measuring window, which means we
effectively measure the bitrate during the measuring window. That's
covered by the test added in that patch though, only it's going through
the new stats API instead of the old one.So, let's just delete them
from the old API for now.

BUG=666725
CC=ehmaldonado@chromium.org
R=kjellander@chromium.org

Committed: https://crrev.com/054f7b1e4a7b3bbf8b1effb31ae4620918fe8787
Cr-Commit-Position: refs/heads/master@{#438474}
==========

[commit-bot: I haz the power, 2016-12-14 09:50:40]

Patchset 1 (id:??) landed as
https://crrev.com/054f7b1e4a7b3bbf8b1effb31ae4620918fe8787
Cr-Commit-Position: refs/heads/master@{#438474}