Linked by Thom Holwerda on Wed 28th Nov 2012 15:17 UTC
Thread beginning with comment 543459
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2005-07-20
There were several "fixes". For example, there's a dual-core optimizer program that AMD wrote and gave to gaming companies to fix XP for their Athlon64 X2 CPUs.
I'm not quite sure what it does, actually, but it seems to help.
There were quite a lot of video drivers that updated to optimize dual-core and hyperthread support for XP. I believe they forced various driver threads onto specific cores so the XP thread scheduler wouldn't get involved.
Some of those tweaks are less optimal now that CPUs have four/eight cores/threads and the Windows 7 and 8 thread schedulers.