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

Best practices for designing S3 prefix for relational DB #188

Open
StrikeW opened this issue Aug 5, 2022 · 0 comments
Open

Best practices for designing S3 prefix for relational DB #188

StrikeW opened this issue Aug 5, 2022 · 0 comments

Comments

@StrikeW
Copy link

StrikeW commented Aug 5, 2022

Hello, I am curious about how Rockset designs object prefixes for those SST files on S3.

Amazon claims that each prefix can support at least 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second. If all SST files store in the root path of the bucket, e.g, s3:https://bucket/, then all requests will to go to the same prefix and meet the performance limits. Would you mind sharing your experience on this?

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

No branches or pull requests

1 participant