Overview
Distributed Rendering (DR) can significantly accelerate your rendering workflows, especially for large and complex scenes. However, to fully take advantage of its benefits, a few best practices should be followed.
Below are several strategies to optimize your distributed rendering setup for maximum efficiency and performance.
Use V-Ray Proxies or .vrscene Exports
It is always a good practice to export heavy geometry objects to V-Ray Proxy (or .vrscene) files. Proxy geometry is not written to the scene file, which makes the scene size smaller, saves render time, memory consumption, and network transfer time. This is also true for the local render. Since the geometry is externalized, rendering becomes more efficient and streamlined.
Copy Assets Locally on each Render Slave
Storing all necessary assets locally on each render node minimizes network traffic and avoids delays caused by large file transfers. This is particularly important for scenes with complex geometry, large textures, or extensive cache data.
Optimize Network Performance
A fast and stable network connection is crucial for efficient distributed rendering. High-speed LAN setups significantly reduce data transmission delays and improve communication between the workstation and render servers.
Use Bucket Sampler for DR Workloads
While the Progressive Image Sampler has benefits in interactive workflows, the Bucket Sampler is generally more suitable for distributed rendering. It scales better across multiple machines and allows for more efficient division of the image into smaller renderable chunks.
Prevent the “Last Bucket Stuck” Issue
When rendering animations, V-Ray cannot start rendering the next frame before all the buckets are complete for the current one. This may slow down the whole process if there is an area of the image that requires a lot more sampling than the rest of it. As a result, one or more buckets can get “stuck” in a specific area, while all other machines are idle and waiting for those few buckets to complete. Reducing the bucket size can help in this case. But avoid using extremely low values, because this can have the opposite effect and reduce the overall performance.
Consider Scene Complexity and Hardware Differences
Depending on how complex the scene is, some of the faster machines may finish rendering the entire image before the slower ones even get a chance to join. If there are big differences in the amount of RAM across your render servers, machines with less memory might not be able to handle very complex scenes and could fail to render at all. To avoid these issues, it’s best to use render machines with similar hardware and enough RAM to handle the demands of your scenes.
Choose a Powerful Workstation as the DR Controller
Since the initiating workstation orchestrates the distributed rendering process, it should be one of the most capable machines in your setup. Its performance directly influences the stability and speed of the overall rendering workflow. Note: The workstation that initiates the rendering process will always be one step ahead, as the scene is already loaded into its memory.
Conclusions
Following these guidelines will help you achieve faster, more reliable results in your distributed rendering pipeline with V-Ray.