hi guys,
when I submit job in Maya 2011 x64, it takes a long time (about 8 sec) to pop up the UI.
if I clicked the “submit job” button, maya is locked. The only thing I can do is waiting.
This drives me crazy. After trying a lot , I found when the DNS in my workstation was
shut down. The plugin worked faster.
But I can’t shut down DNS, there’s other app need it.
Is there other way to solve it?
Thanks for any advices!
Hi Bill,
Can you open a command prompt on this machine and run the following:
deadlinecommand.exe -pools
Actually, run it twice - once with the DNS off and once with it on. Can you let us know if this command runs slower with DNS on?
If it does, check to see if you’re using the repository machine’s hostname or ip address in the UNC path you’re using to connect to it. If it’s the server name, try using the ip address instead.
Cheers,
Hi Ryan,
I tests the command many times, it’s slow when the DNS is on.
The repository address uses ip path.
\192.100.3.103\DeadlineRepository
TD have tested the command with DNS off, and it’s really fast.
Tomorrow I will test it again and let you konw the result.
I did a bit of googling, and found other cases where people using UNC paths experienced slow access. One person’s workaround was to map the UNC path to a mapped drive, and after that, everything was fast again.
As a test, you could map \192.100.3.103\DeadlineRepository to T:, and then use the Deadline Launcher to change your repository path to T:. It would be interesting to see if that made a difference.
Cheers,
Hi, Ryan
I mapped the IP address to local R:, then ran the command “deadlinecommand -pools”,
it was still slow. when I cleared the DNS address, the above command ran as fast as ping,
after Enter is pressed, the result show.
I guess Deadline do some search on DNS, when I clear the DNS address, Deadline return immediately.
if I am wrong, correct me
-Bill
Hi Ryan
I have another question, when I submit job with Maya Plugin in Maya, it’s slow,
but it’s normal fast when submitting job in Deadline Monitor.
I can’t figure out the reason.
The issue seems to be deadlinecommand’s initial connection to the repository over the UNC path. Because google turned up this issue in all sorts of applications, I don’t think it’s a Deadline problem specifically, but a general DNS problem that affects Deadline.
When you submit from the Deadline Monitor, you’re already connected to the repository at this point, which would explain why it’s quicker. When you submit from Maya, deadlinecommand must connect to the repository in order to submit the job.
Cheers,