![]() You didn't specify Windows/Linux/OS-X (even though your terminology sounds rather Windows-like) so I can't offer any specific solutions, but it's the job of the scheduler in your OS to allocate resources, given whatever settings the two software packages provide. I've seen a lot of discussion on such issues and a few FAH enhancements have been submitted, in the long-run, nothing is really satisfactory. ![]() Balancing the needs to two such CPU-limited jobs is a real challenge. Like Handbrake, FAH was designed to soak up all available resources after more important jobs have been given priority. That would keep clear of Handbrake without wasting any cycle time. 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". I could affine Handbrake to stay off a single core, but that ends up wasting > 50% of the core's time because again need is so small. I don't really have any other options than Handbrake and it has no options to pick the number of cores it uses. This becomes a problem for me because within the same priority group, Handbrake apparently takes precedent and ends up suffocating relatively small CPU need. 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. Typically, Handbrake runs at Low priority, essentially just soaking up whatever is left after scheduling everything else. 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). Here's my situation, and off the bat I'll recognize it's a little odd.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |