9acc18d1fe
Today when the pacing debt is cleared, we blindly ask for 50 bytes of padding, which is above a static magic number for RTX payload padding. Instead, we should adjust the target size based on the current padding rate. The old pacer sort-of does this, it allows the budget to grow up to one process interval (usually 5ms). This CL makes the dynamic pacer also use a duration as target, by default 5ms to match old pacer but with a trial to allow tweaking it. This will be important for good behavior due to https://bugs.chromium.org/p/webrtc/issues/detail?id=11508 Bug: webrtc:10809 Change-Id: I9c14acc5730c6e2e0d7821adf5fb058b8d5487c6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/173687 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31091}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct