{"id":1511,"date":"2019-03-27T00:00:00","date_gmt":"2019-03-27T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/high-throughput-with-azure-blob-storage"},"modified":"2025-06-19T04:29:22","modified_gmt":"2025-06-19T11:29:22","slug":"high-throughput-with-azure-blob-storage","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/high-throughput-with-azure-blob-storage\/","title":{"rendered":"High-Throughput with Azure Blob Storage"},"content":{"rendered":"\n

I am happy to announce that High-Throughput Block Blob (HTBB) is globally enabled in Azure Blob Storage. HTBB provides significantly improved and instantaneous write throughput when ingesting larger block blobs, up to the storage account limits for a single blob. We have also removed the guesswork in naming your objects, enabling you to focus on building the most scalable applications and not worry about the vagaries of cloud storage.<\/p>\n\n\n\n

HTBB demo of 12.5GB\/s single blob throughput at Microsoft Ignite<\/h2>\n\n\n\n

I demonstrated the significantly improved write performance at Microsoft Ignite 2018. The demo application orchestrated the upload of 50,000 32MiB (1,600,000 MiB) block blobs from RAM using Put Block<\/a> operations to a single blob. When all blocks were uploaded, it sent the block list to create the blob using the Put Block List<\/a> operation. It orchestrated the upload using four D64v3 worker virtual machines (VMs), each VM writing 25 percent of the block blobs. The total time to upload the object took around 120 seconds which is about 12.5GB\/s<\/b>. Check out the demo in the video below to learn more.<\/p>\n\n\n\n

GB+ throughput using a single virtual machine<\/h2>\n\n\n\n

To illustrate the possible performance using just a single VM, I created a D32v3 VM running Linux in US West2. I stored the files to upload on a local RAM disk to reduce local storage performance affecting the results. I then created the files using the head command with input from \/dev\/urandom to fill them with random data. Finally I used AzCopy v10<\/a> (v10.0.4) to upload the files to a standard storage account in the same region. I ran each iteration 5 times and averaged the time to upload in the table below.<\/p>\n\n\n\n

Data set<\/strong><\/td>Time to upload<\/strong><\/td>Throughput<\/strong><\/td><\/tr>
1,000 x 10MB<\/td>10 seconds<\/td>1.0 GB\/s<\/td><\/tr>
100 x 100MB<\/td>8 seconds<\/td>1.2 GB\/s<\/td><\/tr>
10 x 1GB<\/td>8 seconds<\/td>1.2 GB\/s<\/td><\/tr>
1 x 10GB<\/td>8 seconds<\/td>1.2 GB\/s<\/td><\/tr>
1 x 100GB<\/td>58 seconds<\/td>1.7 GB\/s<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

HTBB everywhere<\/h2>\n\n\n\n

HTBB is active on all your existing storage accounts, and does not require opt-in. It also comes without any extra cost. HTBB doesn\u2019t introduce any new APIs and is automatically active when using Put Block<\/i> or Put Blob<\/i> operations over a certain size. The following table lists the minimum required Put Blob<\/i> or Put Block<\/i> size to activate HTBB.<\/p>\n\n\n\n

Storage Account type<\/strong><\/td>Minimum size for HTBB<\/strong><\/td><\/tr>
StorageV2 (General purpose v2)<\/td>>4MiB<\/td><\/tr>
Storage (General purpose v1)<\/td>>4MiB<\/td><\/tr>
Blob Storage<\/td>>4MiB<\/td><\/tr>
BlockBlobStorage (Premium)<\/a><\/td>>256KiB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Azure Tools and Services supporting HTBB<\/h2>\n\n\n\n

There is a broad set of tools and services that already support HTBB, including:<\/p>\n\n\n\n