Network and distributed rendering

What’s the difference between network rendering and distributed rendering?

Distributed Rendering and Network Rendering are different methods of sending render tasks to multiple render server machines:

Network Rendering sends entire frames (or tasks) to separate render nodes through a render manager. Each node works independently.

Distributed Rendering (DR) and V-Ray Swarm split a single frame across multiple machines at the same time. This accelerates still images and high-resolution frames.

Comparison between network and distributed rendering

• Rendering stage

  Network Rendering is best suited for the final rendering stage where no further project changes are required.

  Distributed Rendering is suitable for both final rendering and design stage rendering. During the project development stage, the artist can speed up the interactive rendering process by harnessing the resources of other machines in addition to the power of the artist's workstation (render-host). 

   

• Efficiency

  Network Rendering: jobs can be rendered sequentially or parallelly, which makes it more efficient when rendering image sequences. 

  Distributed Rendering is efficient for rendering high-resolution still images, where multiple machines render simultaniously, thus decreasing rendering time.

  In DR1, the scene and assets are sent separately to each render node, the loading time of which varies based on the project's complexity.

  In DR2, the scene and assets are sent only to the dispatcher node, which in turn delegates the work to other render servers.
  
  Read more about DR2.

   

• Control / Job Resubmission

  Network Rendering offers control over rendering multiple jobs sequentially or in parallel. Jobs can be prioritized and servers - manually included or excluded. In case of an accidental error, jobs are usually automatically resubmitted.  

  Distributed Rendering allows selecting server machines manually or automatically.  Adding/removing render servers can be done during the rendering process. In case of accidental error, jobs needs to be manually resubmitted. 

   

• Missing assets / Inaccuracy in individual machines

  Network Rendering does not support automatic trasnferral of missing assets. Inaccuracy in individual machines, however, will not affect the rendering of other machines. 

  Distributed Rendering can transfer missing assets from the render host to render servers automatically.  Inaccuracies or issues in individual machines, however, will affect the final rendering.

   

• Software configuration

  Network Rendering: there are many render management software on the market, each requiring different software configuration.

  Distributed Rendering offers native support and does not require additional software configuration. Host Application (excluding 3ds Max) is not required for executing Distributed Rendering jobs.

   

• Operating system support 

  Network Rendering is limited to the OS supported by the host application.

  Distributed Rendering supports any Operating System via V-Ray Standalone. Jobs can also be submitted to machines with different Operating Systems. 

   

• Supported V-Ray versions

  Network Rendering depends on a third-party software. Chaos cannot guarantee that it will support the latest V-Ray integrations.

  Distributed Rendering is developed by Chaos, and is always up to date with any V-Ray integrations.

Additional information

• 3ds Max
• DR2 in 3ds Max
• Maya
• SketchUp
• Rhino
• Revit
• Cinema4D
• Houdini

• Blender

   

Related articles

• Distributed rendering troubleshooting guide