Closed
Bug 1891732
Opened 1 year ago
Closed 1 year ago
nsThreadPool: Let the last running thread steal the next event without waiting if possible
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
DUPLICATE
of bug 1891664
People
(Reporter: jstutte, Unassigned)
Details
Attachments
(1 obsolete file)
Hopefully we can try to optimize the current loop a bit without the need for full logical affinity.
| Reporter | ||
Comment 1•1 year ago
|
||
Experiments so far did not really work out as hoped (as a side effect more threads woke up). I might give this another spin but probably this is a dead end.
| Reporter | ||
Comment 2•1 year ago
|
||
Comment 3•1 year ago
|
||
Comment on attachment 9397238 [details]
WIP: Bug 1891732 - Have an MRU list for idle threads and separate condvars for each thread.
Revision D207785 was moved to bug 1891664. Setting attachment 9397238 [details] to obsolete.
Attachment #9397238 -
Attachment is obsolete: true
| Reporter | ||
Comment 4•1 year ago
|
||
The investigation here made me add that patch to bug 1891664, as its benefits are more general than thread affinity. That patch kind of implements also the intent of this bugs title.
You need to log in
before you can comment on or make changes to this bug.
Description
•