Affinity settings not followed when parking is off

[chadnesbit]

Hi, was using process lasso to assign CCDs on a 9950x3d and it seemed to work.  Then I installed parkcontrol to stop cores from sleeping for better performance.  But with parking disabled, processes are now going onto cores they don't have affinity for.  Any ideas?

[Jeremy Collake]

Like which processes? Games? Some games are protected by anti-cheats and so their CPU affinities need assigned to the game launcher, which they'll then inherit from the next time they are run.

My guess is that when you disabled parking, some of those games were at liberty to use cores they wouldn't have otherwise. You should assign a CCD based CPU affinity to Steam.exe and/or to individual games. A properly applied CPU affinity will not violated (no scheduling of threads outside it).

[chadnesbit]

Hi, Thanks for the response.  Chrome is one example which will show up on CCD0 even though the affinity is set to CCD1.  Process explorer, corsair services, are other examples.  Same process name:number on both CCDs.   Task manager confirms affinity is set only to CCD1. Puzzling. 

The game I'm playing right now (kingdom come deliverance 2) mostly stays on CCD0 but will mildly show up on CCD1.  I've tried adjust the affinity control in the BIOS and also game mode in windows to see if they were overriding.  Didn't seem to change anything.

Thanks,
Chad     

[straightforward]

Hi, was using process lasso to assign CCDs on a 9950x3d and it seemed to work.  Then I installed parkcontrol to stop cores from sleeping for better performance.  But with parking disabled, processes are now going onto cores they don't have affinity for.  Any ideas?

Hi chadnesbit, I haven't had a similar issue with the 9950x3D, but sometimes disabling deep power management features can lead to strange behavior. Are you running the latest versions of both Process Lasso and ParkControl? What version of your OS is it? More details about your system configuration might help people give you more accurate suggestions.

[straightforward]

It is possible that using both Process Lasso and ParkControl to manage cores is causing a conflict. You can try using only one of the two tools to see if the problem is resolved. Both have their own CPU management features.