Does anyone know if it’s actually possible to disable either CCUs or physical cores on a Threadripper PRO (5955WX) in the ASUS WRX80E-SAGE WiFi BIOS?
I found a “Gaming Mode”, whose description implies that it would disable one of the CCUs (and indeed this is a common feature across manufacturers), but turning it on didn’t actually disable one of the CCUs. In OS I still had 32 threads and they were all being utilized. The description for “Gaming Mode” is, in part, “[if Enabled]… the CCD control option will not work any more” and “If user want to use the CCD control under AOD make sure set Gaming Mode as Disable”.
Assuming AOD stands for “AMD Overdrive”, the only option in there for CCD is in Advanced\AMD Overclocking\AMD Overclocking\Precision Boost Overdrive as “CCD Frequency Optimizer”. No options for actually disabling a CCD.
Didn’t see this thread, what problem are you trying to solve by disabling cores?
The state of scheduling in Windows is really bad. I had to turn off hyperthreading on my Saphire Rapids because of the windows issues with over 64 logical processors. Some of the issues have been fixed.
I also use Process Lasso for when I want to restrict apps to a core or group of cores. You can also do that with task manager, but it’s a bit of a PITA. It won’t help of the application is doing it’s own thread management or creating extra threads because it sees a lot of cores.
I’m so flummoxed by Threadripper on Windows at the moment. I’ll have to give more time of day to Process Lasso.
I purchased a Threadripper to help acclimate me to the workstation/server class before pursuing an EPYC system. I had intentions of doing some casual gaming in my free time but have been stifled by a persistent issue in that every time I sit down to play a game I’ll only be able to get a few performant minutes out of my 5995WX. My frames/sec will be superb for a few minutes and then collapse (100 > 20). I can never game at a playable framerate for more than a few minutes.
Might this issue stem from the hostile Windows scheduling you mention? Oddly enough, I was playing for long sessions this past weekend after a fresh chipset update and a UEFI reset. I got greedy for a PBO overclock and have been regretting it for several days now. And of course, I haven’t the slightest clue the order of operations that got it working then. If it ain’t broke don’t fix it!
