So should capacity be stored in a new 'm_max_capacity" similar to pools or keep the old 'm_capacity'?
Anything I can help with or are you already in the process of all these changes?
timurhai wrote: ↑Tue Jun 25, 2019 9:10 am
"You mean the other way around?"
- Sorry i did not got you.
I was able to change the capacity of the pool, but not the render. You wrote "Hmm... It seems that for now WebGUI can set it only for render (not pool)."
timurhai wrote: ↑Mon Jun 24, 2019 9:38 pm
Capacity is implemented. By default it is -1 (no limit), but limited a number of tasks per host (1 per host).
Where can I set it? I can't seem to find it in the GUI.
Come to think of it, one could make a farm.json parser which applies the rules on the farm. If this can be run at startup it would still be compatible with the old setup. I do like the idea that one can add and remove services on-the-fly (which is actually a problem I'm currently facing). Although I...
After seeing that the render pools have been implemented I wanted to give it a spin. I would REALLY miss the farm.json setup. Not having the ability to dynamically assign capacity, services through rules is a BIG loss IMHO. Wouldn't it be better to have rules to assign pools? I don't see the benefit...
Hmm... I think it should be when it evaluates which branch to parent, so server side? Perhaps x amount of levels to ignore and OS specific. Either way it's always possible to override it when submitting I guess..