Render On Your Network
KeyShot Network Rendering allows you to take advantage of your network’s computer resources for rendering images, animations, and KeyShotVR’s. After the simple installation process, any user with KeyShot can send a “job” to be rendered on the network. The jobs are organized into a queue that all users can view. Jobs can also be sent from the internal KeyShot queue to network rendering.
How It Works
KeyShot Network Rendering consists of three elements: Master, Slaves, and Queues. The Master manages all of the connected network resources. The Slave does the actual rendering. The Queue shows the jobs that have been submitted to the Network Rendering system by each Slave. After the job is submitted, the Queue can be closed or disconnected from the network without affecting the jobs.
The more cores you have, the faster your images and animations render.
Manage all of the users in your organization with the ability to assign specific privileges based on role or usage. Easily add, remove or change passwords and privileges for each user all from a single screen within the user management system.
Manage your slave computers, scheduling them for use at specific times or days. Set the number of cores allowed for each slave and see immediately what computers are allocated for use, with the ability to utilize computer power without KeyShot being installed.
Whether you need 32 cores to increase the speed of your smaller rendering processes or 256 cores to bring in the ultimate rendering power, KeyShot Network Rendering has the set-up and scalable options to cut down the time it takes to create renderings and animations.
Note: A virtual core/thread will count as a physical core and is subject to the Network Rendering license’s core limit. For example, an 18 core (36 thread) machine will be calculated as 32 cores by the Network Rendering application.
