Hello,
We are currently experiencing network issues, and I’m trying to adjust the throttling.
We have nuke jobs that have a long loading time but a short computing time.
And we have maya jobs that have a short loading time but a long computing time.
So, ideally, we should have different throttling values depending of the jobs.
Could I do this in deadline ?
Cheers,
Pierre
Not yet. You’re the second person to ask in the last 30 days however (these things always come in pairs!)
I’ll go and make this an internal discussion issue.
One workaround in the mean time might be to create limits which release at 1%. They won’t queue up like they would with throttling, but it should help keep the farm from starting too many of either job at once.
Hello Edwin,
That’s a nice work-around, thank you.
If we use this, there will be no way to limit the slave usage in a pool, am I correct ?
Cheers,
Pierre
Pools and groups can still be used, but the interesting problem is that if the limit is full, the Slave will move onto to find any work it can find. That means that if there is a different job type in a lower priority pool the Slave will skip over the important work and pick whatever it can.
The benefit if having a more granular limit would be that the Slaves would wait for the resource to become available instead of skipping over. Limits aren’t perfect, but it’s the reason Limits have the ability to release at a certain percentage is to work around the exact problem you are having.