Hi,
we do have a few limits for the number of available licenses set of the different software packages. For example, we have 5 Nuke render licenses. The limit of the maximum number of Slaves to wake up is set to 8.
I now saw that for a Nuke job (Hiero actually, but shouldn’t matter here) i sent that 8 machines were started despite the active limit of 5 machines for the job.
I was wondering whether this is a bug or actually normal behaviour. Can’t really tell whether this was different on previous versions as i didn’t pay attention to this before. This is on DL 7.0.1.3.
If it’s not a bug would it be possible to add this as a feature in a future release?
Best,
Holger
Hello Holger,
While I can’t say for sure, the UI and settings are the same on that part of the Power Management window are the same for 6.2.1.50 as they are for 7.0.1.3, so I would imagine they should act the same. I will ask the devs is there is a way to code a check before starting machines to see how many are needed, not just starting the maximum.
Cheers,
hey Dwight,
thanks! When i said earlier versions i actually meant the DL7 beta. We only switched to Deadline during the beta around 3 months ago.
To be a bit picky i’d also like to ask why the setting is called “… maximum number of Slaves…” when it seems to be starting (or at least trying to start) this exact number? 
And while we’re at it: there are some more factors that i think could influence the actual number of machines that should be started. Like e.g. if a job has a number of tasks that’s below that limit. Maybe it’s worth adding that, too. And it’s probably also worth explaining this feature a bit better in the docs. I couldn’t find how it exactly behaves in that section of the manual.
Cheers,
Holger