Transcoding Duration via Reserved-Queue takes way longer then with On-Demand Queue (MediaConvert)

Question

Hi,

we noticed that the transcoding duration differs a lot between the on-demand queue and the reserved queue when transcoding an asset with the exact same encoding-settings.

In particular the asset took about 45min on the **on-demand** queue and about 2h on the **reserved-queue**.

Is that a normal behaviour?

Kind regards,

Riva

Answer

AWS MediaConvert Reserve Transcodes are designed for a low cost transcode solution for a volume of low priority jobs. It is not focused on speed. A Reserved Transcode queue is a fixed slot size, and will run each job as the slot resources will allow. On-demand transcode jobs have the ability to choose between different slot sizes, based on job complexity and size of source file.

If you want to estimate how long a job will take with Reserved Transcode, you can enable the Simulate Reserve queue in the Job Management under Job Settings when running a test job.

Transcoding Duration via Reserved-Queue takes way longer then with On-Demand Queue (MediaConvert)

Conteúdo relevante