http://bugs.winehq.org/show_bug.cgi?id=11674
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2009-01-06 05:16:36 --- (In reply to comment #6)
This suggests that the problem may be the way in which threading is implemented in World of Warcraft, but to study this is kinda out of my reach.
Either that it could be that either WoW decides not to schedule as much work as it does on Windows
I don't know if it'll be useful, but maybe something can be spotted if you add traces to dlls/kernel32/thread.c for some of the functions which don't have traces (CreateThread, SuspendThread, ResumeThread, SetThreadPriority, SetThreadPriorityBoost, SetThreadAffinityMask, SetThreadIdealProcessor) which print the function parameters using the TRACE macro then attach a +thread,+tid log here.