S3 Performance Flashcards

1
Q

What is an S3 prefix?

A
  • An S3 prefix is the part of the file path between the bucket name and the object (ex. ‘mybucketname/folder1/subfolder1/myfile.jpg’ has prefix ‘/folder1/subfolder1’)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does KMS have to do with performance?

A
  • Uploading and downloading files count towards the KMS quota

The exact amount for the quota is region-specific, but is either 5,500; 10,000; or 30,000 requests per second.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How can you request a quota increase for KMS?

A

Currently, there is NO way to request a quota increase for KMS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is Multi-Part Upload?

A
  • The Idea behind Multi-part uploads is to parallelize an upload (and thus increase its efficiency)
  • This is done by splitting a big file into parts and then uploading the individual parts in parallel
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are S3 Byte Range Fetches?

A
  • S3 Byte Range Fetches allow you to speed up downloads by parallelizing them.
  • You parallelize by specifying exact byte ranges
  • If there is a failure in the download, it is only for a specific byte range.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What would you use if you just want to download partial amounts of a file?

A

S3 Byte Range Fetches with just the relevant bytes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

At what file size is Multi-Part Upload recommended?

A

100MB

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

At what file size is Multi-Part Upload required?

A

5GB

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What do S3 prefixes have to do with performance?

A
  • They are important for performance because requests are measured per second per prefix
  • So, y​ou can get better performance by spreading your reads across different prefixes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How many PUT requests can AWS handle?

A

3,500 per prefix per second

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How many COPY requests can AWS handle?

A

3,500 per prefix per second

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

How many POST requests can AWS handle?

A

3,500 per prefix per second

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How many DELETE requests can AWS handle?

A

3,500 per prefix per second

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How many GET requests can AWS handle?

A

5,500 per prefix per second

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How many HEAD requests can AWS handle?

A

5,500 per second per prefix

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a good common way to ensure lots of different prefixes in S3?

A

Go by timestamp of upload

(there are many right answers here)