Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add episode 124 transcript #183

Merged
merged 4 commits into from
May 30, 2024
Merged

Conversation

eoinsha
Copy link
Collaborator

@eoinsha eoinsha commented May 29, 2024

Transcript

This change includes the transcript for the podcast episode, created by Podwhisperer.
The summary below is generated by Episoder.

Episode Summary

In this episode, we discuss some tips and tricks for optimizing performance when working with Amazon S3 at scale. We start by giving an overview of how S3 works, highlighting the distributed nature of the service and how data is stored redundantly across multiple availability zones for durability. We then dive into specific tips like using multipart uploads and downloads, spreading load across key namespaces, enabling transfer acceleration, and using S3 byte-range fetches. Overall, we aim to provide developers building S3-intensive applications with practical guidance to squeeze the most performance out of the service.

Suggested Chapters

01:34 An overview of how S3 works at massive scale in terms of storage volume, request throughput, and data durability.
06:09 Tip 1 - Use multipart uploads and byte range fetches for large objects to improve throughput.
08:38 Tip 2 - Spread load across different key namespaces to avoid throttling.

Suggested Tags

S3, Amazon S3, AWS, performance, optimization, scale, throughput, latency, durability, availability, multipart upload, byte range fetch, concurrency, namespaces, transfer acceleration, cloud storage

Transcription Automation and others added 4 commits May 29, 2024 22:02
@lmammino lmammino merged commit 3cd238e into main May 30, 2024
1 check passed
@lmammino lmammino deleted the ep-124-transcript-20240529220213457 branch May 30, 2024 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants