http://bugs.winehq.org/show_bug.cgi?id=20602
--- Comment #5 from Felix Zielcke fzielcke@z-51.de 2009-11-13 13:17:53 --- (In reply to comment #4)
Is this a regression? If so, could you do a regression test? There were some affinity related patches in 1.1.31.
Thanks somehow I missed/forgot them. The performance for TF2 wasn't always that great for me since I started to play it with wine. I think some 1.1.2x release. So lately I haven't followed much the changes affecting TF2
Anyway, it's not surprising that the last commit with affinity in the commit message causes this behaviour:
commit 474b2e4bfb46cf1bb8db0faa6ecfdb3fd157b117 Author: Juan Lang juan.lang@gmail.com Date: Tue Sep 29 09:17:30 2009 -0700
server: Use kernel support for thread affinity when available.
Then I tried the 1.1.30 release with above commit and the 2 main threads still run on both cores. So the real problem is some of the other commits. I do more testing later. I hope I didn't screw up anything. I think it would be just good if someone else could confirm my testing.