Open
Bug 1706925
Opened 4 years ago
Updated 3 years ago
evaluate the worker thread model
Categories
(Core :: WebRTC, task, P2)
Core
WebRTC
Tracking
()
NEW
People
(Reporter: ng, Unassigned)
References
(Blocks 1 open bug)
Details
Evaluate the worker thread model (one thread pool, 4 threads) to see whether:
One thread pool is fine, or if we’re better served by one pool per TaskQueue type (so the thread pool is the same for that type across all calls).
4 threads is enough. Especially if betting on the single-pool case.
Reporter | ||
Updated•4 years ago
|
Comment 1•3 years ago
|
||
NB we already made a change to the model, where the call taskqueue (process global) sits on its own (single thread) thread pool, to avoid getting starved out by all the worker taskqueues (often per-stream or per-call). The size of the worker thread pool remains to be evaluated.
You need to log in
before you can comment on or make changes to this bug.
Description
•