Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

KeyShot Network Rendering consists of three roles:  Clients, Manager, and Workers.
The figure shown below illustrates the simplest interaction between the roles, where each computer only has one role.

A computer configured as a manager and/or worker can also function as a client. In the manager's case, KeyShot (the client application) communicates internally with the manager service which runs in the background.

It is important to note that there should only be one manager on the network! Click here, if you need to have multiple managers on your network.

The Manager can have both CPU and GPU workers connected, and will assign the tasks of a CPU/GPU render job to the type of workers that are relevant in each case. A worker can be set up to be available for CPU/GPU/both types of jobs if the hardware meets requirements.


Client

Manager

Worker

  • Sends job requests to the manager (via KeyShot).
  • Receives completed jobs from manager.
  • Saves final output to specified location.
  • Can modify certain configurations of the manager, like users.


  • Receives job requests from clients and places them in a queue.
  • Divides each job into computation tasks.
  • Assigns tasks to each worker.
  • Compiles all rendered output into a final image, video, KeyShotXR or configuration.
  • Sends completed jobs back to clients.
  • Receives rendering tasks from manager that it computes.
  • Sends completed task results back to manager.




  • No labels