Page 1 of 1

CGRU is too fair!

Posted: Thu Aug 10, 2017 3:11 am
by avclubvids
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?

Re: CGRU is too fair!

Posted: Mon Aug 14, 2017 8:20 pm
by keyframe
You can up the user's priority.

Seems to act more or less god-like here when set to 255.

G

Re: CGRU is too fair!

Posted: Tue Aug 15, 2017 2:31 pm
by timurhai
Hi.
Sorry for a delay.
What do you mean by "god" or "absolute" priority?
Afanasy threats each priority point as 10% resources bonus during balancing:
http://cgru.info/afanasy/user#user_priority
Default priority is 99. If you set some other priority to 199 (give it more 100 points), you will have 1.1^100 bonus.
This is 13780.6 times more resources than 99.
So if have 13781 machines, the entire farm will some 199 job, except 1 machine.
If you have less than 13780 machines, 99 will never run while 199 has ready tasks.

Re: CGRU is too fair!

Posted: Tue Aug 15, 2017 8:37 pm
by avclubvids
I was under the impression that 99 was the top due to the submitter's "-1" leading to a priority of 99, we'll try much higher numbers and see how it goes!

Re: CGRU is too fair!

Posted: Wed Aug 16, 2017 9:06 am
by timurhai
Globally in the CRGU "-1" commonly means "use default/configured value".
For priority it is 99:
https://github.com/CGRU/cgru/blob/maste ... t.json#L70