Ideally speaking, the OS should run on core 0 while apps run on 1, 2 and 3... though Windows never prioritizes it this way since it goes for the first available core, and that can be core 0 if the OS is idle. The second it kicks out of idle, though, it will grab the first available core and if WoW isn't using core 1 at this very second but is using core 0 then it loses its optimization when it requires core 1 but its unavailable so it jumps to core 2.
Worth actually doing the mod? If you can show me actual proof of a difference that's not 1% then I'd say it's worth it.
Well I can't speak with numbers but I assure you this cpu tweak helped me a lot(5-10 more fps if I remember correctly) on my i7 2600. So I will use it again in 1 week hoping it still does its trick. I can come back with the results.
CPU processAffinityMask CVar:
Patch 3.3.2 (2010-02-01): Manually adjusting this cvar is no longer needed unless you're trying to run the game on specific cores. It is now uncapped so it will run on whatever core your OS deems as fit.
Source: http://www.wowpedia.org/CVar_processAffinityMask
TCPNoDelay registry key:
Blizzard disabled nagling at the application level (effectively integrating the TCPNoDelay function into the game client) way back in patch 2.3.2 and they added a checkbox to enable/disable it on-demand in patch 4.1.
Source: http://www.wowinterface.com/portal.p...731&pageid=246
Core parking:
No idea. Wouldn't do it personally.
DX11:
Can be set in the ingame options menu.
Last edited by cremor; 2013-03-06 at 09:12 AM.
Reason: Made links clickable.