CGRU is too fair!
Posted: Thu Aug 10, 2017 3:11 am
The decision of how many slaves each render gets is a weighted combination of submit time, priority, and user, where the farm is "fairly" divided amongst all users and all jobs. This is great for a general render condition, where there are a bunch of users and many machines and no high urgency for a specific render to be completed ASAP.
BUT, it is extremely common for a single render to have very high, even total priority. The only way in CGRU to get the entire farm on that job is to pause all other jobs, and then unpause them later, or to guess a time to set them to unpause, or to manually make them dependent on the top priority job. This is not ideal, as there are situations in which we need to quickly let a render through, but then have the farm return to business as normal. We need a "god mode" for render priority, where we can essentially say "this render gets 100% of available resources until it is done".
What are the suggested ways to do this sort of thing, to break the balanced approach CGRU uses in order to allow the admin to determine which render(s) get absolute priority?
BUT, it is extremely common for a single render to have very high, even total priority. The only way in CGRU to get the entire farm on that job is to pause all other jobs, and then unpause them later, or to guess a time to set them to unpause, or to manually make them dependent on the top priority job. This is not ideal, as there are situations in which we need to quickly let a render through, but then have the farm return to business as normal. We need a "god mode" for render priority, where we can essentially say "this render gets 100% of available resources until it is done".
What are the suggested ways to do this sort of thing, to break the balanced approach CGRU uses in order to allow the admin to determine which render(s) get absolute priority?