SAA-C03 ยท High-performing storage
Amazon S3 performance
Request rates per prefix, multipart upload, S3 Transfer Acceleration, byte-range fetches and S3 Select style retrieval of subsets of data.
Key points
- Per partitioned prefix: at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD /s; more prefixes multiply it.
- Gradual scaling: 503 Slow Down meanwhile.
- Multipart upload: parts 5 MiB-5 GiB, up to 10,000, parallel, retried singly; from ~100 MB.
- Transfer Acceleration: CloudFront edges, s3-accelerate endpoint, DNS-compliant name, no periods.
- Byte-range fetch: HTTP Range header.
- S3 Select: closed to new customers; use byte ranges or Athena.
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html
Practice questions
At least how many GET/HEAD requests per second can an application achieve per partitioned prefix in an S3 bucket?
- 1,000
- 3,500
- 5,500
- 55,000
Show answer
Answer: C. 5,500
S3 supports at least 5,500 GET/HEAD requests per second per partitioned prefix. The 3,500 figure is the write rate (PUT/COPY/POST/DELETE), and 55,000 is what ten prefixes could reach together.
Which statements about S3 multipart upload are true?
- Parts can be uploaded in parallel and in any order
- A failed part can be resent without restarting the whole upload
- Every part, including the last one, must be at least 5 MiB
- Incomplete uploads are deleted automatically after 24 hours
- One upload can contain up to 100,000 parts
Show answer
Answer: A. Parts can be uploaded in parallel and in any order, B. A failed part can be resent without restarting the whole upload
Parts can be uploaded independently, in parallel and in any order, and a failed part is simply sent again. Only the last part may be smaller than 5 MiB, an upload allows at most 10,000 parts, and incomplete uploads never expire on their own, so a lifecycle rule with AbortIncompleteMultipartUpload is used to clean them up.
S3 request rate limits apply per bucket, so splitting data across several buckets is the only way to exceed 3,500 writes per second.
Show answer
Answer: False
False. The request rates apply per partitioned prefix, and a bucket can have any number of prefixes. Spreading keys across several prefixes in the same bucket raises the aggregate rate.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
