http://bugs.winehq.org/show_bug.cgi?id=11674
Alexey Loukianov mooroon2@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mooroon2@mail.ru
--- Comment #178 from Alexey Loukianov mooroon2@mail.ru 2012-06-12 21:22:03 CDT --- I'm not sure if this bug is _de_facto_ obsolete or not, but the observed behavior of the Diablo III running under Wine exactly fits under definitions of this bug: under Wine I've got several D3 threads but only one of them uses CPU (around 90-95% of one core), rest are mostly idle. Under native OS with the same D3 installation I've got entirely different CPU usage situation: with "default" affinity D3 process utilizes 4 of 8 cores, each core is hogged for about 50%. When I change CPU affinity of D3 process myself limiting it to only use CPU 0 and 2 (i.e. I want the game to use two cores of my AMD FX CPU that do not share the same FP blocks) the game tasks both of these cores to around 80-85%.
I believe that this is one of the core reasons the game performing under Wine way worse than it performs on native producing low FPS that seems to be CPU limited (i.e. it remains almost the same when I switch from 1680x1050 down to 800x600 resolution while standing near waypoint at the middle of the Act I town).