What would be a proper way to make Deadline Monitor to update the Slave List more often? Prior to the MongoDB driven Deadline we’ve used a manual Refresh Slaves command to update the Monitor’s Slave View.
There is no a such command available with the latest Deadline version. Sometimes Deadline Monitor doesn’t list the newly added Slaves at all. Those non-listed Slaves are still running and render the jobs. But the Slave View remains empty.
Ive tried to use Pulse. But it doesn’t help. Closing and re-opening Deadline Monitor also doesn’t update the Slave View. Sometimes Deadline Monitor would list the computers as the slaves that are no longer run the Slave application.
Apparently the Deadline Monitor is somewhat out of sync the way I configured it. Please advise.
Hi,
Are you using Deadline v7.0? Can you confirm your exact version of Deadline? If you’re on v7.0, make sure you’re running at least v7.0.1.3, as this fixes a slave panel update issue. (v7.0.3.0 is actually the latest). Updates are all available via the same download link that our sales team sent you to download v7.0 previously. Feel free to contact sales [at] thinkboxsoftware [dot] com if you need the link re-sending.
Performance Settings and it’s “Auto Adjust” makes it super easy to ‘performance-tune’ your renderfarm to your exact size:
docs.thinkboxsoftware.com/produc … e-settings
Literally, press the “Auto Adjust” button, type in your total number of slaves. Done!
Can you share your current settings and also what those settings look like after you use the “Auto Adjust” button? Hopefully, something will stand out as the issue here.
If you really need to, you can re-expose the manual “refresh” button, but really the auto-refresh is a much more convenient way to work.
docs.thinkboxsoftware.com/produc … e-settings
Thanks for the info Mike!
I am using Deadline 7.0.2.3.R.
Monitor Settings > Enable Manual Refreshing: it is great to know this old school way of refreshing Monitor is still available.
Performance Settings > Auto Adjust is what I was looking for. Mine numbers/settings were by some reason way too high. No wonder it was lagging behind.
Thanks again!