...
A Job is what's submitted by a client to the Supervisor. It's a small bundle of information that includes all the information the Worker will need to execute the job - what program(s) to run, where the source files are, who's what user is running it, how many CPUs it wants, what OS it can run under, etc. When a job is submitted to the Supervisor, it's assigned a unique jobID, that is incremented by the supervisor with each job, (e.g jobID 12345 would be assigned to the job that's submitted immediately after jobID 12344.)
When a job gets spread over multiple Workers, we say that each worker Worker is running an Instance - even if a job is only run on one machine, that machine is running the single Instance.instance of that job. Note: Instances were called Subjobs in Qube! before version 6.4.
Instances (or Job Processes) are numbered 0 through n, where n is the number of processes that the job can run at the same time. Therefore if you want to have the farm render 10 frames at a time, the number of Instances for that job should be 10. Note: Instances were called Subjobs in Qube! before version 6.4.
| Note |
|---|
The "Job CPUs" field specifies the number of Instances for a given job – it does not denote the actual number of processor cores to use when rendering. |
Agenda items (or Frames) refers to the granular list of items to be processed. Let's look at a simple example:
Job 12345 wants to render 4 frames (numbered 100-103) on two workers.
One way that might work out would be like this:
- The (4) four agenda items are: frame 100, frame 101, frame 102, and frame 103.
- Instance 12345.0 renders frames 100 and 102 (agenda items 1 and 3)
- Instance 12345.1 renders frames 101 and 103 (agenda items 2 and 4)
...