I’m curious what the thoughts on the benefits of doing this? I’m just curious if the possibility is there to alleviate load on the network by doing this.
Hello James,
If you submit the scene file it will copy to the repository, though each machine using it would still need to copy it from there. I guess it depends on the connections your repository has to the machines as compared to the connection they have to the current hosting machine.
That’s what i thought, I just wanted to verify. Thanks!
i believe you have 3 options - submit a job location on your server, submit a copy to the repository or submit a copy to a 3rd location. that 3rd location could be a fast-access tier of storage depending on your network infrastructure.
there is an advantage to submitting the copy to the repository that i’ve seen in production - you have a working copy that can’t accidentally be modified. depending on your environment i’ve seen people submit a job that links to the server, and mid render someone else changes that scene file and bang - what you render isnt what you thought you were, or worse yet, you end up with rendered frames that change mid-render.
the other advantage is that you can retrieve the submitted file. i’ve seen cases [usually in previs] where things are changing quickly and the director will buy off on a specific version, but that version doesnt match the render on the server because an animator tweaked something and saved over the same tk. you can rerender or retrieve the submitted file from deadline and work with that, knowing it is identical to the render.
in essence, deadline becomes a simple asset management tool, for archival, reference and small redundancy if you use it this way.
cb