In response to the discussion that occurred in this thread, I did a little bit of analysis with my currently-installed software on how well tasks stick to one core.
Here are my notes:
Some things to note: all analysis is subjective, making use of the Windows task manager for a few seconds of gameplay while no other processor-intensive programs were running. When I state "one CPU," then usage of the second CPU is only a couple percent. While it might be interesting to go back and look at the performance of games where there was some apparent task switching, the three where it may have been of issue aren't easy to benchmark (and neither is performance much of a concern, fortunately).
Please note that in all cases where it looked like there was some task switching between the CPU's, one CPU seemed to remain dominant.
So, from this little analysis, it seems to me that there isn't a significant problem on Windows XP SP2 of tasks switching unecessarily between processors.
Here are my notes:
Code:
BG: One CPU
BG2: One CPU
Doom3: Fair use of dual-core (90%-50%)
FEAR: Not much CPU usage: none of second core
FF7: One CPU
GTA:SA: Mild switching (80%-20%)
Morrowind: Mild Switching (80%-20%)
NWN: Mild Switching (80%-20%)
GalCiv: Altarian Prophecy: Little Switching (90%-10%)
zSNES: One CPU
Some things to note: all analysis is subjective, making use of the Windows task manager for a few seconds of gameplay while no other processor-intensive programs were running. When I state "one CPU," then usage of the second CPU is only a couple percent. While it might be interesting to go back and look at the performance of games where there was some apparent task switching, the three where it may have been of issue aren't easy to benchmark (and neither is performance much of a concern, fortunately).
Please note that in all cases where it looked like there was some task switching between the CPU's, one CPU seemed to remain dominant.
So, from this little analysis, it seems to me that there isn't a significant problem on Windows XP SP2 of tasks switching unecessarily between processors.