AWS Thinkbox Discussion Forums

Minimizing token use by creating a custom node picking function

Let’s say I have a render farm with Deadline in service mode. I have a software that takes tokens based on if that software was opened during the day.

What I want to achieve is a function that takes into consideration if a computer already opened that specific software during the day. If it already has, then use that node for that specific job, if it hasn’t, then try to find another node. If no node exist and if I put the priority to >90 (let’s say) then and only then will it the node pick up the job and render.

What I ultimately want to do is to minimize the number of nodes that opens this software, while having a relatively high traffic flow of renders going through, which is difficult of course.

That sounds like a good upgrade for the limits function
https://docs.thinkboxsoftware.com/products/deadline/10.3/1_User%20Manual/manual/limits.html

I guess for now this would need to be run via a custom script where the job checks a list and creates a pool / group / limit for any job based on the contents of that job.

This also depends if you have any other job limits/pools/groups also, as they’d need consideration also.

is this the flex token thing? Always feels like the fairground token system!

Privacy | Site terms | Cookie preferences