in deadlinemonitor, there are “mantra settings” for mantra jobs. the “threads” option maxes out at 16. we have 12 core machines with hyperthreading so we have 24 threads available. when setting up the job, we can pass in 24 threads without a problem, but if we do any manipulations using the monitor, we can’t get more than 16 threads working on a frame.
it would probably also be worth adding a toggle to simply not pass the # of threads and let the process use all available threads.
Hello,
Deadline doesn’t support specifying more than 16 threads.
We actually were a bit confused here.
If you would want to use all 24 cores on the machine, setting the thread count to zero should allow Mantra to use every core the machine has.
Secretly, under the hood, zero would do exactly what you described. We wouldn’t touch the thread count.
right, okay. i’ll use 0 then. i should have thought of that.
curious, tho, why would deadline monitor limit mantra to 16 threads?
Hello,
So I am pretty sure this is just something we coded in, but I think we can change it in the next build.
Well, back when we wrote the slider years back, 16 seemed like a pretty safe number. It’s like Y2K all over again!
We are upping the numbers across the board if I’m remembering right. When you see Deadline 7, you should be able to choose up to 128! Until 128 is too small… Then who knows.