Maybe if you set the priority and affinity on the stager app, that remains loaded for the full run, will the worker inhered the setting, or you could try Process Lasso. That will do it for you, automated, but you risk the consequence that if e.g. 3 of GFAM on a quad are running and you set the affinity to core 2 and 3 for the science, that you get 2 jobs running on 1 core. BOINC could not care and Process Lasso just follows instructions. The difference between elapsed and CPU time will become huge IIRC when I was experimenting with it to get HPF2 to always run on core 3 (Q6600).

--//--

The science-thread isn't running on Low priority, it runs on Idle priority. Setting the process-priority to BelowNormal has zero effect, since any thread running at Idle priority is only affected if the process-priority is increased to real-time, and you definitely don't want to run it as real-time. While you can use Task Manager and similar to set the process-priority, you can't use Task Manager to set individual thread-priorities. (most WCG-processes has atleast 2 threads).


Locking the affinity can have unexpected effects, since atleast back in the days I ran SETI "classic" any newly-started application that was allowed to use all cpus had a bad habit of choosing the cpu there the affinity-locked process was already running, and in the process leaving a cpu idle. But granted this was with win2k, so hopefully later OS has gotten better cpu-scheduler.