KeyShot Forum

Technical discussions => Extending KeyShot => Network Rendering => Topic started by: Bruno F on December 10, 2018, 11:29:20 am

Title: Network Rendering Best Practices
Post by: Bruno F on December 10, 2018, 11:29:20 am
Network Rendering Best Practices
A job's total processing time is equal to the sum of the file transfer time and render time. In this page, you will find best practices for minimizing your network's total processing time and for maximizing performance.

Processing Time = Transfer Time + Render Time

Network Configuration
KeyShot Network Rendering's performance is subject to your network connection and configuration. To obtain the best results:

CPU Specs
KeyShot Network Rendering's performance is dependent on your CPU/processor specs. To obtain the best results, select a high performance processor that is within your budget. If you’re not sure, consult a computer professional, consumer reviews, and/or CPU benchmarks. (https://www.keyshot.com/forum/index.php?board=36.0)

Memory (RAM)
For optimal performance, each machine should have enough RAM to load the operating system and your largest KeyShot scene.

Job Complexity
KeyShot Network Rendering performance is also subject to job complexity. To obtain the best results, render these kinds of jobs:

File Size
The file size affects the file transfer time. To minimize file transfer time, keep the BIP/KSP file size small.

Linearity
In an ideal render farm, doubling the core count cuts the render time in half. To obtain maximum linearity between core count and render time:

*Computer count should not be confused with core count. If the number of render tasks in a job is less than or equal to the current computer count, then adding more computers will not have any effect on the render speed for that job.