FAQ: How does the Icechunk schema impact s3's partitioned prefix limits

[jhamman]

Problem

As a user looking to get maximal performance out of S3, I may be curious how Icechunk's chunk key schema impacts s3's partitioned prefix limits.

your application can achieve at least 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per partitioned Amazon S3 prefix.

Suggested Improvement

Add a section to the docs explaining expected behavior. Bonus to compare it to vanilla Zarr or NetCDF which are even more likely to suffer from the hot-key issue.