Gnubg's CLI has a "set priority" function that allows to run it with a lower priority, or, theorically, a higher one, but the latter never worked on Unix and hasn't in Windows for some time (it may have in the past but now you would need no run it with elevated privileges to do this, a dubious idea).
Recently Issac tried to add something in the GUI to set this priority more easily, but this doesn't works well since the lower setting is autosaved and you cannot raise it back to the default without editing the gnubgautorc file... The whole idea may have been useful 20 years ago when consumer grade CPUs had only one core, but I'm inclined to think that now one would share the computer resources between an interactive gnubg instance (or other software) and a rollout by running them with a number of threads lower that the number of CPU cores. For instance using 2 threads by default on a 4 cores CPU. Would anyone mind if the feature was entirely removed? If you use it, could you explain in what circumstances? And how effective it really is?
