Comparison of Windows 11 scheduler behavior for AMD vs Intel processors in computing tasks
Comparison of Windows 11 scheduler behavior for AMD vs Intel processors in computing tasks
I tried to skip extra programs whenever possible. The last time I did was to work around issues with multiple CCX on Zen 2 and earlier, but it wasn’t ideal either. If a dual CCD AMD CPU becomes available, I might consider it again. Right now I’m holding back from buying multiple-CCD AMD CPUs, even though that would restrict me to an 8-core setup. That should work for a single gaming system at most. I’m currently using PowerShell commands: $Process = Get-Process BOINC $Process.ProcessorAffinity = 21845 The affinity setting should be changed based on your system’s core count. The main drawback is I can only start it after BOINC begins, and any work it started before isn’t carried over. I also forget to set it up at the right time. I’ll need to investigate how BOINC manager interacts with BOINC itself, which could make things more complicated—I might have to adjust my approach. No worries about that yet.
Certainly, that's a valid observation. To reduce manual effort, consider wrapping your BOINC launch within a scheduled task or service that includes the affinity mask from the start. This ensures the mask is applied automatically when BOINC begins, rather than relying on a script later. For instance, using Task Scheduler to trigger a PowerShell command with the required flags and processor affinity. Alternatively, you can create a service with elevated privileges or use `sc create` to launch BOINC under a wrapper script. While not as elegant as native configuration, this approach guarantees consistent execution in the correct affinity context every time.
My 7800X3D setup was mainly designed for gaming, which is my main focus. Unless I'm traveling far from home, I likely dedicate most of my time to it. It's mostly used on PrimeGrid during competitions to boost performance. It isn't a continuous 24/7 operation nor a constant cruncher. I favor BOINC but prefer it not to start automatically, and if I stop it, I want it completely stopped—not just paused. I believe this could be resolved by manually launching the main process with specific priorities, then starting the manager as usual. The manager's affinity settings shouldn't affect its tasks. I can close the manager normally, which is currently configured to also shut down the client. There might be room for improvement, especially since a PrimeGrid challenge begins soon.