Limitations of Azure Storage (Blobs) RRS feed

  • Question

  • I have searched to see if there are any documented limits to the number of blobs a storage account can have.

    We are investigating the possibility of using an Azure storage account to store a large quantity (and volume) of documents. These documents are a mix of things like PDF documents, photographs, video clips and audio clips.

    Our application (on mobile devices) can use a local database which the user can use to search and identify which document(s) they need to view. This can then be downloaded to the device and viewed/played.

    We have tested this on a small scale (using only a few dozen documents), and it all works well. However, we now want to scale up the data storage side. We have approximately 130GB of documents, split over around 25000 separate documents.

    Some documents are related (for example, part specification data, images, and installation/removal guides), so we have something like part code (six digits) and a document number (two digits). On our original system, we store these in a hierarchy using 10 top level folders 0...9 using the last digit of the part code, with each part code having it's own folder, containing all the documents. Thus, if we know a part code we can map to a document, like

    Part code 001759, document 02 (How to adjust the one-shot PIT interval)


      -- a generic extension is used, the database has metadata explaining how to interpret the data, in this case, as a PDF.

    Obviously, we could simply upload the files "as is" to a single container, since none of the names clash.

    However, are there limits and/or performance implications on doing this, should we implement our existing scheme, or is there a better mechanism for organising the files?

    Of course, we don't know whether this would even work, or whether we are exceeding any storage limits.


    Friday, July 18, 2014 2:10 PM


  • Hi Steve;

    Microsoft Azure does not limit you in terms of the  number of blobs one can create, we only calculate storage limits which currently is 500 TB.

    Listed below is the reference::

    Storage Limits (1)

    Resource Default Limit

    TB per storage account (2)


    Max IOPS for persistent disk

    500 (3)

    Max IOPS per storage account


    Max ingress per storage account (US Regions)

    10 Gbps if GRS(4) enabled, 20 Gbps with it disabled

    Max ingress per storage account (European and Asian Regions)

    5 Gbps if GRS(4) enabled, 10 Gbps with it disabled

    Max egress per storage account (US Regions)

    20 Gbps if GRS(4) enabled, 30 Gbps with it disabled

    Max egress per storage account (European and Asian Regions)

    10 Gbps if GRS(4) enabled, 15 Gbps with it disabled

    1. For more details on these limits, see Azure Storage Scalability and Performance Targets.

    2. For page blobs only pages that are in-use accrue capacity usage. For example, a Virtual Machine with a

    3.127 GB VHD but with only 30 GB being used by the OS, is only billed for the used 30 GB portion within the VHD, not the entire 127 GB.

    4. Geo-Redundant Storage.

    Refrence :: here
    Friday, July 18, 2014 3:03 PM