You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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://bucket/, then all requests will to go to the same prefix and meet the performance limits. Would you mind sharing your experience on this?
The text was updated successfully, but these errors were encountered:
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://bucket/
, then all requests will to go to the same prefix and meet the performance limits. Would you mind sharing your experience on this?The text was updated successfully, but these errors were encountered: