Support GZIP & DEFLATE Content-Encoding for List Blobs Responses
For collections with large numbers of blobs, the XML response payload easily approaches 100s of MBs. In our testing, each block of 5000 objects resulted in a ~2.8MB response. This is without any other flags set (i.e. no snapshots, no metadata, no uncommitted blobs). The response XML is highly compressible. In our testing we saw a 93% size reduction. (2.8MB -> 210KB). This would be a huge improvement in transfer performance, and a large cost savings in egress bandwidth situations.
Thank you for your feedback. Transfer compression will address this ask and is on our backlog. As soon as we have progress to share, we will do so. For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
This is very much need feature where I do not want to enable CDN and can enabled compression at storage level. Alternatively I can have a function tigger whenever someone copies the file and convert into compressed file
Other similar APIs impacted here GetBlockList and PutBlockList - large numbers of blocks (>10k) easily cost over a MB simply due to XML overhead.
(For carification, this referrs to the Azure Blob Storage Service.)