Force client to spawn Cores at given Priority
Posted: Sat Jul 28, 2018 5:18 pm
Here's my situation, and off the bat I'll recognize it's a little odd. Right now I have a single GPU folding pretty much non-stop; concurrently, my CPU spends a lot of time running Handbrake (video encode/decode). Typically, Handbrake runs at Low priority, essentially just soaking up whatever is left after scheduling everything else. The problem is that, even when the Folding Core priority option set to "Slighty Higher", each job's Core is still spawned at Low priority. This becomes a problem for me because within the same priority group, Handbrake apparently takes precedent and ends up suffocating F@H's relatively small CPU need.
I don't really have any other options than Handbrake and it has no options to pick the number of cores it uses. I could affine Handbrake to stay off a single core, but that ends up wasting > 50% of the core's time because again F@H's need is so small. So I'm wondering if there's a way to force the Wrapper to spawn Cores at a specific priority, in my case "Below Normal". That would keep F@H clear of Handbrake without wasting any cycle time. Thanks!
I don't really have any other options than Handbrake and it has no options to pick the number of cores it uses. I could affine Handbrake to stay off a single core, but that ends up wasting > 50% of the core's time because again F@H's need is so small. So I'm wondering if there's a way to force the Wrapper to spawn Cores at a specific priority, in my case "Below Normal". That would keep F@H clear of Handbrake without wasting any cycle time. Thanks!