I’m running into this issue where the Deadline Monitor takes a very long time to load when connecting to a network share. I realize this could be a mix of issues, between network speeds, protocol usage, and Deadline configuration.
Monitor spends what appears to be an excessive amount of time (read: most of boot time) synchronizing plugin icons. This is from a Linux (CentOS 7) client to a RHEL 7 server using SAMBA as the share/transfer protocol. Network speed was 10-10 Mbps.
2018-09-19 17:03:16: Time to initialize: 116.000 ms 2018-09-19 17:03:20: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration 2018-09-19 17:03:41: Auto Configuration: Picking configuration based on: linstat / 192.168.0.117 2018-09-19 17:03:41: Auto Configuration: No auto configuration could be detected, using local configuration 2018-09-19 17:03:41: Time to connect to Repository: 21.396 s 2018-09-19 17:03:41: Time to check user account: 91.000 ms 2018-09-19 17:03:41: Time to purge old logs and temp files: 5.000 ms 2018-09-19 17:05:37: Time to synchronize plugin icons: 1.923 m 2018-09-19 17:05:38: Time to initialize main window: 691.000 ms 2018-09-19 17:05:38: Main Window shown 2018-09-19 17:05:38: Time to show main window: 30.000 ms
Any help on determining why this happens would be great. I also have the server restricted to only a few submission scripts (Arnold, Maya, RenderMan, Modo, Blender) and that list has a 99% chance of never changing. Would it be possible to disable this sync on startup? Paths for the plugin executables might change as updates are added, but Monitor doesn’t need to be aware of that, does it?