Using on-demand queues in AWS Elemental MediaConvert
Your default queue is an on-demand queue. On-demand queues differ from reserved queues in
how AWS Elemental MediaConvert allocates transcoding resources for jobs and in how you pay. For
more information, see MediaConvert Pricing
Topics
Managing resources and testing performance
Manage resources to process even more jobs in parallel. Perform testing to optimize performance.
Resource allocation and job prioritization
By default, your account has one on-demand queue. You can create additional on-demand queues. The Service quotas documentation lists the maximum number of queues available to your account in an AWS Region.
Each queue can simultaneously process a number of jobs up to the maximum listed in the Service quotas documentation. For example, if you have five queues in us-east-1, you can process a total of 1000 jobs simultaneously. (In this example, you can process up to 200 jobs in any individual queue.)
When a job in an on-demand queue finishes, MediaConvert selects the next job to process based on the job's priority. You set the priority of a job when you create it. If more than one job has the highest priority, MediaConvert begins the one that you submitted first. For more information, see Job priority.
You can also organize your jobs with multiple on-demand queues. For example, you might run jobs for different workflows in separate queues. MediaConvert processes these jobs across multiple queues in parallel. You can use Tags to keep track of jobs with different workflows as well.
Note
If you need to process more jobs in parallel, instead of creating additional
queues we recommend that you first request an increase to the number of jobs
your queues can run. To do so, open the Service Quotas
Performance testing
We recommend that you test any workflow with specific performance requirements. By
default, MediaConvert optimizes the performance of your queue for the most
common job types. If your workflow primarily includes a large number of jobs
that complete quickly, or if you have a question about your queue's performance,
contact AWS
support
How you pay for transcoding with on-demand queues
With on-demand queues, you pay based on usage. For pricing details, see AWS Elemental MediaConvert pricing
Create an on-demand queue
AWS Elemental MediaConvert provides a default on-demand queue. A default queue is available in all AWS Regions. Other queues appear only in the AWS Region where they are created. To add additional resources to your account, you can create your own on-demand queues.
To learn how queues affect the way that MediaConvert allocates the processing of resources, see Managing resources and testing performance. The following tabs show different options for creating an on-demand queue.
Pause and reactivate on-demand queues
New queues default to an Active status and are available to
process jobs immediately. You can optionally Pause a queue to
stop processing any additional jobs. When you pause jobs, MediaConvert finishes
processing jobs that are already running. If you submit a job to a paused queue, its
status will remain in SUBMITTED until you change the queue's status
back to Active or cancel the job.
The following tabs show how to change the status of an on-demand queue.
Listing on-demand queues
You can list the queues that are associated with your AWS account and get details about those queues. The following tabs show different options for listing queues.
Delete an on-demand queue
You can delete any queue other than the default queue. You can't delete a queue that contains unprocessed jobs. The following tabs show how to delete an on-demand queue.
