Issue 1

Internal block size for COG seems like an endless discussion.

Tilebench won't solve everything but with luck and nice reproducible process we will have a better understanding.


Blue - internal blocks
Red - Mercator grid

### Methods
Input project has quite an effect so we should make sure to test with several projection

Tools:
- https://github.com/developmentseed/morecantile
- https://github.com/geospatial-jeff/async-cog-reader (compute internal blocks shapes)
- GDAL / Rasterio

### Expected results
- Timings (S3 latency and data transfer)
- Number of GET Called
- Transfered byte

### Dataset
- Sentinel 2 - Int16 1band
- Naip - 3 bands Byte

Ref:
https://github.com/opendatacube/benchmark-rio-s3/blob/master/report.md
https://github.com/vincentsarago/rio-tiler-bench
https://github.com/vincentsarago/gdal-http2-benchmark
https://github.com/vincentsarago/awspds-benchmark

Start with Tilebench and the linked morecantile and async-cog-reader tools, then review the GDAL/Rasterio benchmarking references. Build a reproducible comparison across projections using Sentinel 2 and NAIP datasets; done means reporting S3 latency and transfer timings, GET request counts, and transferred bytes.

Written by the indexing model from the issue text.