We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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?
s3://mybucket/somelayer/{z}/{x}/{y}
uri
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?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
If I use
s3://mybucket/somelayer/{z}/{x}/{y}as myuritemplate, aren't we introducing a performance issue due to the way S3 stores data?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?
The text was updated successfully, but these errors were encountered: