[Bug 36692] Bad performance when combineng SetEvent / WaitForSingleObject for synchronizing worker threads
wine-bugs at winehq.org
wine-bugs at winehq.org
Sat Jun 7 18:12:48 CDT 2014
http://bugs.winehq.org/show_bug.cgi?id=36692
Sebastian Lackner <sebastian at fds-team.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sebastian at fds-team.de
--- Comment #2 from Sebastian Lackner <sebastian at fds-team.de> ---
I would like to point out the following wine-devel discussion about the same
topic:
http://www.winehq.org/pipermail/wine-devel/2014-April/104088.html
Especially this comment by
* Vincent Povirk, that exaplains why it is so difficult to optimize the speed
of SetEvent/WaitForMultipleObjects:
http://www.winehq.org/pipermail/wine-devel/2014-April/104090.html
* and this comment by me, which explains the differences between the different
sets of synchronization primitives:
http://www.winehq.org/pipermail/wine-devel/2014-April/104092.html
At my opinion its very difficult to optimize the speed of these specific
functions, but as Bruno already wrote, some (minimal) test code would probably
be useful - especially to measure how "bad" the performance really is compared
to Windows.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list