Manage speed and concurrency of your encoding

media services logo


This article gives a brief overview of how you can manage speed and concurrency of your encoding jobs/tasks.

Overview

In Media Services, a Reserved Unit Type determines the speed with which your media processing tasks are processed. You can pick between the following reserved unit types: S1, S2, or S3. For example, the same encoding job runs faster when you use the S2 reserved unit type compare to the S1 type. The scaling encoding units topic shows a table that helps you make decision when choosing between different encoding speeds.

In addition to specifying the reserved unit type, you can specify to provision your account with Reserved Units. The number of provisioned reserved units determines the number of media tasks that can be processed concurrently in a given account. For example, if your account has five reserved units, then five media tasks will be running concurrently as long as there are tasks to be processed. The remaining tasks will wait in the queue and will get picked up for processing sequentially when a running task finishes. If an account does not have any reserved units provisioned, then tasks will be picked up sequentially. In this case, the wait time between one task finishing and the next one starting will depend on the availability of resources in the system.

For detailed information and examples that show how to scale encoding units, see this topic.

Next step

Scale encoding units

Media Services learning paths

Media Services v3 (latest)

Check out the latest version of Azure Media Services!

Media Services v2 (legacy)

Provide feedback

Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. You also can go directly to one of the following categories: