7950X3D - About CPU sets, rules, gaming and performance mode

Started by TheRealBix, January 03, 2024, 01:05:26 PM

Previous topic - Next topic

TheRealBix

Hi there

I've used Process Lasso for a while on "manual mode", setting manually each process affinites etc. Time has come to do things properly.

CPU affinity is great for games, when EAC doesn't enter the bar, then I use CPU sets. I have two main rules :

(0-15) for f:\games\*
(16-31) for /^([^,]*,){2}(?!system,|registry,|memory compression,|secure system,)/

Together with some specific CPU affinity rules, this works great for games. However...
I'm a bit disappointed by Windows CPU sets which, at least from my testing by forcing high CPU loads with 32 threads, behave exactly like affinities. jobs won't populate CCD0 threads in any of my tests.

Instead, I'm now running everything on (0-31) and searching for a way to trigger the rule (16-31), either with performance mode or on process start...

I can't really find how to do that, do you have any clue ? I'm not familiar with every available tools.

Thanks for reading

TheRealBix

Ok I found a way, tho not that elegant... It may serves for others.

I'm using Profile Switcher to change between two profiles : Game and Desktop. The only key difference between those is the (16-31) rule from Game is (0-31) for Desktop.
Added a rule in Profile Switcher for actual games and specific softwares to trigger the Game profile.

Not elegant because the switch isn't fast, do not care if processes are foreground/background, and tedious because I must update both profiles for each update modification I must do.

Jeremy Collake

It looks like you found the best way, at least for the time being. You are right that the Config Profile Switcher isn't very intuitive to use. We're working on further improvements in this area!
Software Engineer. Bitsum LLC.

Garouga

Quote from: TheRealBix on January 03, 2024, 01:05:26 PMHi there...I'm a bit disappointed by Windows CPU sets which, at least from my testing by forcing high CPU loads with 32 threads, behave exactly like affinities. jobs won't populate CCD0 threads in any of my tests...

I came to the same conclusion regarding the CPU sets behaving like affinities.

My current (workaround) setup:
1. Disabled the AMD 3D Cache optimizer during the driver install
2. Disabled Windows Game mode
3. Rules for games to be restricted to the 3D Cache (0-15)
4. BIOS Setting (Asrock): Advanced-->AMD CBS-->SMU Common Options-->CPPC Preferred: Frequency. This is probably not necessary, since the default behavior (Auto) without Windows Game mode is to use the high frequency cores first anyway.

This basically means that everything runs on all CPUs (0-31) using the high frequency CPPC (16-31) first, while games are restricted to the 3D Cache CPUs (0-15).

Not ideal, but only a few games benefit from using CPU (16-31) in addition to the 3D Cache (0-15) and they have high enough frame rates to be GPU bound anyway.