[Webkit-unassigned] [Bug 43150] Investigate using the thread pool instead of a dedicated thread for WorkQueue on Windows

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=43150


Adam Roben (aroben) <aroben at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Investigate using thread    |Investigate using the
                   |pool instead of a dedicated |thread pool instead of a
                   |thread for WorkQueue on     |dedicated thread for
                   |Windows                     |WorkQueue on Windows




--- Comment #2 from Adam Roben (aroben) <aroben at apple.com>  2010-08-05 09:35:05 PST ---
We probably wouldn't want to do this until we had switched to using an I/O completion port in WorkQueue (bug 43148).

But I'm not so sure this will work well for us, at least not with ::RegisterWaitForSingleObject. That function will cause a new worker thread to be spawned every time the I/O completion port is signaled, even if another thread is already processing a message from the completion port. This is OK for correctness, as the worker thread will then immediately block on ::GetQueuedCompletionStatus until the other thread(s) finish their work. But it could mean that lots of threads end up sitting around blocked on ::GetQueuedCompletionStatus if it takes longer for a message to be processed than it takes for the completion port to get signaled again.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.