Deadline Cloud jobs
A job is a set of instructions that AWS Deadline Cloud uses to schedule and run work on available workers. When you create a job, you choose the farm and queue to send the job to.
A submitter is a plugin for your digital content creation (DCC) application that manages creating a job in the interface of your DCC application. After you create the job, you use the submitter to send it to Deadline Cloud for processing.
The submitter creates an Open Job Specification (OpenJD) template that describes the job.
At the same time it uploads your asset files to an Amazon Simple Storage Service (Amazon S3) bucket. To reduce upload
time, the submitter only sends files that have changed since the last upload to Amazon S3. For more
information about OpenJD, see the OpenJD
specifications
You can also create a job in the following ways.
-
From a terminal – for users submitting a job that are comfortable using the command line.
-
From a script – for customizing and automating workloads.
-
From an application – for when the user's work is in an application, or when an application's context is important.
For more information, see How to submit a job to Deadline Cloud in the Deadline Cloud Developer Guide.
A job consists of:
-
Priority – The approximate order that Deadline Cloud processes a job in a queue. You can set the job priority between 0 and 100, jobs with a higher number priority are generally processed first. Jobs with the same priority are processed in the order received.
-
Steps – Defines the script to run on workers. Steps can have requirements such as minimum worker memory or other steps that need to complete first. For example, a job can have one step that renders the frames of a scene, and a second step that uploads thumbnails of the finished frames to your project tracker after the render step completes. Each step has one or more tasks.
-
Tasks – A unit of work sent to a worker to perform. A task is a combination of a step's script and parameters, such as a frame number, that are used in the script. The job is complete when all tasks are complete for all steps.
-
Environment – Set up and tear down instructions shared by multiple steps or tasks.
Topics
Control job worker limits and priority
Use job-level controls to limit how much fleet capacity one job can use and to determine which waiting jobs receive workers first:
- Maximum worker count
-
Limits the number of workers that can process a job at the same time. Other jobs can use the remaining workers in the fleet. Set this value when you submit the job or change it later in the Deadline Cloud monitor.
deadline bundle submit my_job --max-worker-count 50 - Priority
-
Determines the approximate order in which jobs receive available workers. Higher-priority jobs generally run before lower-priority jobs. Jobs with the same priority run in the order received.
For information about changing these properties after submission, see Using the Deadline Cloud monitor.
