If the request workload is typically a mix of GET, PUT, DELETE, or GET Bucket (list objects), choosing appropriate key names for the objects ensures better performance by providing low-latency access to the S3 index. Workloads that include a mix of request types. S3 best practice guidelines can be applied only if you are routinely processing 100 or more requests per second. If the typical workload involves a request rate for a bucket to more than 300 PUT/LIST/DELETE requests per second or more than 800 GET requests per second, it’s recommended to open a support case to prepare for the workload and avoid any temporary limits on your request rate. If the typical workload involves only occasional bursts of 100 requests per second and less than 800 requests per second, AWS scales and handle it. S3 can achieve at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per prefix in a bucket. 
If the request rate grows steadily, S3 automatically partitions the buckets as needed to support higher request rates.
S3 scales to support very high request rates.Reference S3 Best Practices Performance Multiple Concurrent PUTs/GETs
0 kommentar(er)
