I would like to create a limit to accommodate a plugin that uses a license per task. If I set a limit of 10 but concurrent tasks of 2, does that mean it will try to pull 20 licenses?
This is a known limitation between limit groups and concurrent tasks. Currently, a slave will only acquire one limit stub, regardless of the concurrent task count. This makes it difficult to manage software that is licensed once per instance, rather than once per machine.
If this particular job type will always have the same concurrent task setting, then what you could do is set the limit to be the license count divided by the concurrent task count. For example, if you have 10 licenses, and will always be rendering with concurrent tasks equal to 2, then you could set the limit to 5. That way, while there is the possibility your licenses aren’t fully utilized (ie: a slave is only rendering 1 task instead of 2), at least you’ll never go over your license count.
We are aware of this limitation, and are working on adding the necessary pieces to Deadline 6 to better handle this case at some point during the 6.x release cycle. We plan to allow you to specify if the limit should be per machine or per task.
Hope this helps,
- Ryan
Thanks Ryan, that helps. I’ll watch for this in Deadline 6.