Express Processing Assets

Standard processing queue

The standard processing queue for VOD content follows FIFO (first in first out) logic. Every customer can process 10 jobs in parallel (unless their contract indicates higher, as there is additional cost). So if more than 10 assets are ingested at the same time, the rest of the assets remain in the queue and are processed based on FIFO. Often, one of the assets uploaded later might need to be processed first due to time sensitive nature of the content. To support this use case, OoyalaADAPT has an “Express processing queue”.

Express processing queue

For every customer, in addition to the standard processing queue, an express processing queue is available. The express processing queue can process five jobs in parallel (unless their contract indicates higher, as there is additional cost). Consider the express processing queue as a carpool or high volume lane in a highway. Once a job is submitted to the express processing queue, it gets higher priority than jobs in standard processing, and is picked ahead of jobs in the standard processing queue. However, the express processing queue also uses the FIFO logic and any more than five assets submitted to this queue remain queued until an open slot is available.

Note: If you submit all jobs to the express processing queue, then there is no difference between the standard and express queues.

How to use the Express Processing Queue

Note: You cannot edit or delete express transcoding that is set already. If you need this to be removed for any reason, please contact Ooyala Support.
There are currently three ways to submit jobs to a job to the express processing queue:
  • During manifest-based content ingestion, add the following new metadata tag to indicate express processing:
    <ooyala:metadata name="express_asset">true</ooyala:metadata>
  • If an asset has already been ingested to the standard processing queue, you can use the API to move it to the express processing queue.
    • Set priority for already created assets

      Set express transcoding after an embed is created or for content replacements.

      PATCH /v2/assets/:embed  
                    {
                    "transcoding_priority" : "express"
                    }
  • When you upload content via the backlot API, you can also indicate express processing.
    • Create a new asset

      Add an attribute named "transcoding_priority" : "express" while creating a new asset.

      POST /v2/assets/
                    {
                    "name": "My two-minute long video",
                    "file_name": "my_source_file.avi",
                    "asset_type": "video",
                    "file_size": 412895,
                    "chunk_size": 100000,
                    "transcoding_priority" : "express"
                    }
    • Include a new attribute

      The GET /v2/assets/:id API includes a new attribute if express transcoding is selected.

      GET /assets/:id
                    {
                    "transcoding_priority" : "express"
                    }
                  
    • Validations
      • New attributes are allowed for asset types "video", "audio", and "ad". For any other asset types, the API responds with the HTTP 400 message:
        Attribute transcoding_priority is allowed for asset types video, audio, ad
      • The value should be "express" for new attributes. For any other value, the API responds with the HTTP 400 message:
        transcoding_priority should be 'express'

Frequently Asked Questions

Q: What is the default concurrency limit of the standard processing queue?

A: The default concurrency limit of the standard processing queue is 10 jobs. A job includes all outputs (HLS,DASH, MP4 etc.) associated with the processing profile.

Q: What is the default concurrency limit of the express processing queue?

A: The default concurrency limit of the express processing queue is five jobs. A job includes all outputs (HLS,DASH, MP4 etc) associated with the processing profile.

Q: Can I have a higher concurrency limit for my standard/express processing queue?

A: There is an additional cost for a higher concurrency limit, unless stated in your contract. Please contact your account manager for further details.

https://help.ooyala.com/sites/all/libraries/dita/en/video-platform/concepts/express_process.html

Was this article helpful?