s3 uri template and performance
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
If I use `s3://mybucket/somelayer/{z}/{x}/{y}` as my `uri` template, aren't we introducing a performance issue due to [the way S3 stores data](https://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate-perf-considerations.html#workloads-with-mix-request-types)?
My understanding from the link is that all of my tiles would be serving from the same partition, which is contrary to S3 best practices.
Does this just mean that S3 is not ideal as a tile store? Or are there other tricks to using it more effectively?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked AWS S3 request-rate guidance and the repository's `uri` template entry point. Determine whether the documented S3 tile-storage behavior needs clarification, and define done as a clear recommendation about partitioning, performance expectations, and any effective usage guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100