2

There is a Windows service which ingests Video files which are delivered by some content providers. Then the Windows Service tries to create renditions for each given video file using Amazon Elastic Transcoder.

For each video file around 15 renditions are created through creating one Job and then adding 15 outputs to it.

This works perfectly until I run my test project a few times in a row. Then I get this error message "Your application is submitting requests to Amazon Elastic Transcoder faster than the maximum request rate".

I get an error when I just test the logic of my Windows service whilst at production capacity this Windows Service will ingest around 50,000 video files every day. That means I will creating 50,000 jobs every day as well. For such a high volume of request Elastic Transcoder seems to be too weak.

Is there a configuration to increase the throttling on Elastic Transcoder? If there is not, what is the actual limit of crating jobs per minute?

4

1 回答 1

1

这是我找到的一些文档。

简而言之：

  • 对于每个区域，每个 AWS 账户 4 个管道
  • 排队作业的最大数量：每个管道 100,000
  • 您可以以持续的速率为每个 AWS 账户每秒提交两个 Create Job 请求；允许每秒 100 个请求的短暂突发。

换句话说，你不应该对每天 50k 个工作有问题，只要你在任何持续的时间段内不以高于 2 个工作/秒的速度提交它们。

于 2015-09-09T07:58:49.107 回答