Support for multiple byte ranges on blob read/write
We need random read (and later write) access to thousands of discrete ranges (each in the order of a few KBs) within very large binary blobs (in the order of 100s of GB). The current APIs force us to submit a single request for each such range. One negative aspect is billing, of course, but the main problem is the client-side and network loads for handling all these requests!
We would like to ask for the byte range support to be extended to multiple ranges (e.g. "bytes=from0-to0, from1-to1, ...").
The API should of course specify a maximum number of ranges - in the order of 100s would be extremely welcome!
Being billed per range might be acceptable (but hopefully at a reduced rate, because of the reduction in network traffic). The main value comes from the potential performance gain for our applications with these access patterns.
Alternatively, are there other relevant APIs or solutions available? (SO question here: https://stackoverflow.com/questions/57870494/support-for-multiple-byte-ranges-on-azure-blob-read-write)
Lander Erzeel commented
We have a similar access pattern on large blob files (streaming point cloud data), and would like to request this feature as well (albeit only for reading). The smaller the average range size, the bigger the win on performance and efficiency.