http://bugs.winehq.org/show_bug.cgi?id=11674
Claudiu Curca Alexstrasza2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Alexstrasza2@gmail.com
--- Comment #6 from Claudiu Curca Alexstrasza2@gmail.com 2009-01-06 04:27:07 --- Confirmed on Gentoo 2008.0, running kernel 2.6.27-gentoo-r7 and wine 1.1.10 on an AMD Turion64 X2
The CPU load for Wow.exe is 105% max during gameplay. It spikes up to 140% during instance load-time, but once it's loaded it goes down to ~100% using only one single core.
Setting the ProcessAffinityMask in Config.wtf to "3" or any other value seems to not have any effect.
Also tested on a DUAL processor Intel Pentium III at 1GHz each, using Debian Etch and wine 1.1.12 compiled from sources. The behavior is exactly the same as described above.
Out of curiosity, I've tested the threading capabilities of wine and found them to be (not surprisingly) in working condition.
To do this, I've compiled a 'worker' app in visual studio. Basicly, it's a simple exe which spawns 2 threads and simulates 'working' in them. The exe is called HardWorker.exe and it's attached to this comment.
(Note: To run it you may need the Visual C 2005 Runtime (roughly 2MB). download it from http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-... and install it with wine.)
The results were clear. HardWorker.exe bites ~195% of the CPU time when ran. 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.