Don't boost pacing rate after pause.

Don't boost pacing rate after pause.

The pacer has a mechanism to make sure all packets are sent within some
time limit. This is based on the average queue time of the packets in
the pacer queue.

If the pacer is paused while packets are still in the queue (for
instance if the underlying transport goes down temporarily), on resume
all those packets might be past the time limit and thus will all be
burst out onto the network in a tight loop.

This CL subtracts pause time from the queue time, effectively pausing
the clock for the queue while the pacer is paused, so that when we
resume the pacing bitrate will be the same as when we paused.

BUG=webrtc:7694
Review-Url: https://codereview.webrtc.org/2994323002
Cr-Commit-Position: refs/heads/master@{#19367}
Committed: https://chromium.googlesource.com/external/webrtc/+/ddcfb9fc6a5a41b3d6fd8a2524b6a607072118d7

[sprang_webrtc, 2017-08-16 10:34:22]

The CQ bit was checked by sprang@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2017-08-16 10:34:31]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[sprang_webrtc, 2017-08-16 10:34:32]

sprang@webrtc.org changed reviewers:
+ philipel@webrtc.org

[philipel, 2017-08-16 11:08:05]

lgtm

[commit-bot: I haz the power, 2017-08-16 12:07:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-08-16 12:07:24]

Dry run: This issue passed the CQ dry run.

[sprang_webrtc, 2017-08-16 12:36:17]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2017-08-16 12:36:22]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2017-08-16 12:38:50]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1502886977768570, "parent_rev":
"5b9746ef10a3042abd766430197fd1bc0dade648", "commit_rev":
"ddcfb9fc6a5a41b3d6fd8a2524b6a607072118d7"}

[commit-bot: I haz the power, 2017-08-16 12:39:03]

Description was changed from

==========
Don't boost pacing rate after pause.

The pacer has a mechanism to make sure all packets are sent within some
time limit. This is based on the average queue time of the packets in
the pacer queue.

If the pacer is paused while packets are still in the queue (for
instance if the underlying transport goes down temporarily), on resume
all those packets might be past the time limit and thus will all be
burst out onto the network in a tight loop.

This CL subtracts pause time from the queue time, effectively pausing
the clock for the queue while the pacer is paused, so that when we
resume the pacing bitrate will be the same as when we paused.

BUG=webrtc:7694
==========

to

==========
Don't boost pacing rate after pause.

The pacer has a mechanism to make sure all packets are sent within some
time limit. This is based on the average queue time of the packets in
the pacer queue.

If the pacer is paused while packets are still in the queue (for
instance if the underlying transport goes down temporarily), on resume
all those packets might be past the time limit and thus will all be
burst out onto the network in a tight loop.

This CL subtracts pause time from the queue time, effectively pausing
the clock for the queue while the pacer is paused, so that when we
resume the pacing bitrate will be the same as when we paused.

BUG=webrtc:7694

Review-Url: https://codereview.webrtc.org/2994323002
Cr-Commit-Position: refs/heads/master@{#19367}
Committed:
https://chromium.googlesource.com/external/webrtc/+/ddcfb9fc6a5a41b3d6fd8a252...
==========

[commit-bot: I haz the power, 2017-08-16 12:39:04]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/webrtc/+/ddcfb9fc6a5a41b3d6fd8a252...