In #916, the raster loader is used to inject Zarr support into the engine for inline loading when required. In the PR, the interface allows for issuing multiple requests at once; however, some implementations still only issue one request at time.
This is inefficient because often load requests can be issued in batches and waited on in serial (although, there would be one serial loop in each partition). For Zarr in particular, it is particularly inefficient if multiple bands are getting fetched that happen to come from the same chunk. At the very least, issuing all band load requests at once for a single raster will probably help quite a bit and reduce the reliance on caches.
In #916, the raster loader is used to inject Zarr support into the engine for inline loading when required. In the PR, the interface allows for issuing multiple requests at once; however, some implementations still only issue one request at time.
This is inefficient because often load requests can be issued in batches and waited on in serial (although, there would be one serial loop in each partition). For Zarr in particular, it is particularly inefficient if multiple bands are getting fetched that happen to come from the same chunk. At the very least, issuing all band load requests at once for a single raster will probably help quite a bit and reduce the reliance on caches.