Make WebRTC task queues run on chromium's SequencedTaskRunner.
This changes the previous 1:1 TQ:thread relationship and associates WebRTC task queues with Chromium's thread pool. The effect of this is that PeerConnection objects, will start to share threads for "rtc_event_log", "EncoderQueue" and "call_worker_queue". Constructing an instance of PeerConnection will be much less costly and likely not cost any extra thread creation at all, which is why we currently have a limit on the number of instances that we allow creating. Change-Id: Ifd218c5e14e2ce634fd428606e9713a815bd8205 Bug: 808801 Reviewed-on: https://chromium-review.googlesource.com/890738 Commit-Queue: Tommi <tommi@chromium.org> Reviewed-by:Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#542246}
Showing
Please register or sign in to comment