37195cf2e5
The TQ Pacer schedules delayed task according to target time of PacingController. It drains all valid ProcessPackets() in single loop, denies retired scheduled tasks, and round up the timeout to 1ms. This CL also improves packet size estimation in TQ Pacer by removing zero initialization, and introduces `include_overhead_` configuration. Tests: 1. webrtc_perf_tests: MaybeProcessPackets() calls 2075147 -> 2007995 2. module_unittests: MaybeProcessPackets() calls 203393 -> 183563 3. peerconnection_unittests: MaybeProcessPackets() calls 66713-> 64333 Bug: webrtc:13417, webrtc:13437 Change-Id: I18eb0a36dbe063c606b1f27014df74a65ebfc486 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/242962 Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36179}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation