f715618eee
RTCPReceiver initially used a std::map, which made RTCPReceiver::IncomingPacket's use of std::map represent ~0.45% CPU in highly loaded media servers. Using std::unordered_map in change 216321 reduced it only slightly, to 0.39%. This is the second attempt to reduce it even further. By using a flat_map and taking advantage of the increased cache locality, the hope is that it will be reduced. These maps generally have low cardinality (indexed by SSRC), and are looked up often, but modified less often, which make them a potential candidate for flat_map. Bug: webrtc:12689 Change-Id: I6733ccf3484d1c54e661250fb6712971b80fa2a9 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/225203 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34432}
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