amazon-s3 - 有没有人达到 Amazon S3 存储桶的读取或写入上限？

Question

S3 缩放是否存在已知限制？有没有人有过如此多的同时读取或写入，以至于存储桶开始返回错误？我对写入比读取更感兴趣，因为 S3 很可能针对读取进行了优化。

Answer 1

Eric 的评论已经在概念层面对其进行了总结，如常见问题解答 What happens if traffic from my application suddenly spikes? 中所述。还有:

Amazon S3 was designed from the ground up to handle traffic for any Internet application. [...] Amazon S3’s massive scale enables us to spread load evenly, so that no individual application is affected by traffic spikes.

当然，您仍然需要考虑可能的问题并调整 [your] Application for Repeated SlowDown 错误(请参阅 Amazon S3 Error Best Practices ):

As with any distributed system, S3 has protection mechanisms which detect intentional or unintentional resource over-consumption and react accordingly. SlowDown errors can occur when a high request rate triggers one of these mechanisms. Reducing your request rate will decrease or eliminate errors of this type. Generally speaking, most users will not experience these errors regularly; however, if you would like more information or are experiencing high or unexpected SlowDown errors, please post to our Amazon S3 developer forum http://developer.amazonwebservices.com/connect/forum.jspa?forumID=24 or sign up for AWS Premium Support http://aws.amazon.com/premiumsupport/. [emphasis mine]

虽然很少见，但这些减速确实会发生 - 这是 AWS team response说明这个问题(虽然很过时):

Amazon S3 will return this error when the request rate is high enough that servicing the requests would cause degraded service for other customers. This error is very rarely triggered. If you do receive it, you should exponentially back off. If this error occurs, system resources will be reactively rebalanced/allocated to better support a higher request rate. As a result, the time period during which this error would be thrown should be relatively short. [emphasis mine]

您关于读与写优化的假设也在那里得到证实:

The threshold where this error is trigged varies and will depend, in part, on the request type and pattern. In general, you'll be able to achieve higher rps with gets vs. puts and with lots of gets for a small number of keys vs. lots of gets for a large number of keys. When geting or puting a large number of keys you'll be able to achieve higher rps if the keys are in alphanumeric order vs. random/hashed order.