locked
Azure blobs - Few larges or Multiple smalls RRS feed

  • Question

  • I'm creating a very large database of images on Azure, several TB's. The images are grouped in sets of about 150,000 images. Each images are pyramided and tiled which means about 60 chunks per image. So about a 1,000,000 chunks per set.

    The images will never be accessed in their entirety, only specific chunks according to the required resolution (pyramid level) and the region of interest (tile) of the image.

    Would you recommend:

    (A) Keep one big blob of 50GB and keep track of the position and length of each chunk externally (SQL Database) so you can later retrieve the chunk you need...

    -OR-

    (B) Create a 1,000,000 blobs of about 8KB in one container for the whole set and use the blob URI to retrieve the right chunk per convention.

    B is more attractive to me but I worry that the indexing of those blobs by Azure will cause some lag to retrieve the blobs randomly accessed among 1,000,000's of them?

    Friday, August 19, 2016 2:10 PM

All replies

  • Hi,

    Thank you for posting here!

    We are checking on the query and would get back to you soon on this.

    I apologize for the inconvenience and appreciate your time and patience in this matter.

    Regards,

    Vikranth S.

    Saturday, August 20, 2016 12:00 PM
  • Any new information?
    Friday, August 26, 2016 7:27 PM