This article helps you estimate the cost to transfer blobs by using AzCopy.
All calculations are based on a fictitious price. You can find each price in the sample prices section at the end of this article.
The cost to uploadWhen you run the azcopy copy command, you'll specify a destination endpoint. That endpoint can be either a Blob Service endpoint (blob.core.windows.net) or a Data Lake Storage endpoint (dfs.core.windows.net) endpoint. This section calculates the cost of using each endpoint to upload 1,000 blobs that are 5 GiB each in size.
If you upload data to the Blob Service endpoint, then by default, AzCopy uploads each blob in 8-MiB blocks. This size is configurable.
AzCopy uses the Put Block operation to upload each block. After the final block is uploaded, AzCopy commits those blocks by using the Put Block List operation. Both operations are billed as write operations.
The following table calculates the number of write operations required to upload these blobs.
Calculation Value Number of MiB in 5 GiB 5,120 PutBlock operations per blob (5,120 MiB / 8-MiB block) 640 PutBlockList operations per blob 1 Total write operations (1,000 * 641) 641,000Tip
You can reduce the number of operations by configuring AzCopy to use a larger block size.
After each blob is uploaded, AzCopy uses the Get Blob Properties operation as part of validating the upload. The Get Blob Properties operation is billed as an All other operations operation.
Using the Sample prices that appear in this article, the following table calculates the cost to upload these blobs.
Price factor Hot Cool Cold Archive Price of a single write operation $0.0000055 $0.00001 $0.000018 $0.000011 Cost of write operations (641,000 * operation price) $3.5255 $6.4100 $11.5380 $7.0510 Price of a single other operation $0.00000044 $0.00000044 $0.00000052 $0.00000044 Cost to get blob properties (1000 * other operation price) $0.0004 $0.0004 $0.0005 $0.00044 Total cost (write + properties) $3.53 $6.41 $11.54 $7.05Note
If you upload to the archive tier, each Put Block operation is charged at the price of a hot write operation. Each Put Block List operation is charged the price of an archive write operation.
Cost of uploading to the Data Lake Storage endpointIf you upload data to the Data Lake Storage endpoint, then AzCopy uploads each blob in 4-MiB blocks. This value isn't configurable.
AzCopy uploads each block by using the Path - Update operation with the action parameter set to append. After the final block is uploaded, AzCopy commits those blocks by using the Path - Update operation with the action parameter set to flush. Both operations are billed as write operations.
The following table calculates the number of write operations required to upload these blobs.
Calculation Value Number of MiB in 5 GiB 5,120 Path - Update (append) operations per blob (5,120 MiB / 4-MiB block) 1,280 Path - Update (flush) operations per blob 1 Total write operations (1,000 * 1,281) 1,281,00After each blob is uploaded, AzCopy uses the Get Blob Properties operation as part of validating the upload. The Get Blob Properties operation is billed as an All other operations operation.
Using the Sample prices that appear in this article, the following table calculates the cost to upload these blobs
Price factor Hot Cool Cold Archive Price of a single write operation $0.00000715 $0.000013 $0.0000234 $0.0000143 Cost of write operations (1,281,000 * operation price) $9.1592 $16.6530 $29.9754 $18.3183 Price of a single other operation $0.00000044 $0.00000044 $0.00000068 $0.00000044 Cost to get blob properties (1000 * operation price) $0.0004 $0.0004 $0.0007 $0.0004 Total cost (write + properties) $9.16 $16.65 $29.98 $18.32 The cost to downloadWhen you run the azcopy copy command, you'll specify a source endpoint. That endpoint can be either a Blob Service endpoint (blob.core.windows.net) or a Data Lake Storage endpoint (dfs.core.windows.net) endpoint. This section calculates the cost of using each endpoint to download 1,000 blobs that are 5 GiB each in size.
If you download blobs from the Blob Service endpoint, AzCopy uses the List Blobs to enumerate blobs. A List Blobs is billed as a List and create container operation. One List Blobs operation returns up to 5,000 blobs. Therefore, in this example, only one List Blobs operation is required.
For each blob, AzCopy uses the Get Blob Properties operation, and the Get Blob operation. The Get Blob Properties operation is billed as an All other operations operation and the Get Blob operation is billed as a read operation.
If you download blobs from the cool or cold tier, you're also charged a data retrieval per GiB downloaded.
Using the Sample prices that appear in this article, the following table calculates the cost to download these blobs.
Price factor Hot Cool Cold Price of a single list operation $0.0000055 $0.0000055 $0.0000180 Cost of listing operations (1 * operation price) $0.0000055 $0.0000055 $0.0000180 Price of a single other operation $0.00000044 $0.00000044 $0.00000052 Cost to get blob properties (1000 * operation price) $0.00044 $0.00044 $0.00052 Price of a single read operation $0.00000044 $0.000001 $0.00001 Cost of read operations (1000 * operation price) $0.00044 $0.001 $0.01 Price of data retrieval (per GiB) $0.00 $0.01 $0.03 Cost of data retrieval 1000 * (5 * operation price) $0.00 $50.00 $150.00 Total cost (list + properties + read + retrieval) $0.001 $50.001 $150.011 Cost of downloading from the Data Lake Storage endpointIf you download blobs from the Data Lake Storage endpoint, AzCopy uses the List Blobs to enumerate blobs. A List Blobs is billed as a List and create container operation. One List Blobs operation returns up to 5,000 blobs. Therefore, in this example, only one List Blobs operation is required.
For each blob, AzCopy uses the Get Blob Properties operation which is billed as an All other operations operation. AzCopy downloads each block (4 MiB in size) by using the Path - Read operation. Each Path - Read call is billed as a read operation.
If you download blobs from the cool or cold tier, you're also charged a data retrieval per GiB downloaded.
The following table calculates the number of write operations required to upload the blobs.
Calculation Value Number of MiB in 5 GiB 5,120 Path - Update operations per blob (5,120 MiB / 4-MiB block) 1,280 Total read operations (1000 * 1,280) 1,280,000Using the Sample prices that appear in this article, the following table calculates the cost to download these blobs.
Price factor Hot Cool Cold Price of a single list operation $0.0000055 $0.0000055 $0.0000065 Cost of listing operations (1 * operation price) $0.0000055 $0.0000050 $0.0000065 Price of a single other operation $0.00000044 $0.00000044 $0.00000052 Cost to get blob properties (1000 * operation price) $0.00044 $0.00044 $0.00052 Price of a single read operation $0.00000060 $0.00000130 $0.00001300 Cost of read operations (1,281,000 * operation price) $0.73017 $1.6653 $16.653 Price of data retrieval (per GiB) $0.00000000 $0.01000000 $0.03000000 Cost of data retrieval 1000 * (5 * operation price) $0.00 $50.00 $150.00 Total cost (list + properties + read + retrieval) $0.731 $51.666 $166.653 The cost to copy between containersWhen you run the azcopy copy command, you'll specify a source and destination endpoint. These endpoints can be either a Blob Service endpoint (blob.core.windows.net) or a Data Lake Storage endpoint (dfs.core.windows.net) endpoint. This section calculates the cost to copy 1,000 blobs that are 5 GiB each in size.
Note
Blobs in the archive tier can be copied only to an online tier. Because all of these examples assume the same tier for source and destination, the archive tier is excluded from these tables.
Cost of copying blobs within the same accountRegardless of which endpoint you specify (Blob Service or Data Lake Storage), AzCopy uses the List Blobs to enumerate blobs at the source location. A List Blobs is billed as a List and create container operation. One List Blobs operation returns up to 5,000 blobs. Therefore, in this example, only one List Blobs operation is required.
For each blob, AzCopy uses the Get Blob Properties operation for both the source blob and the blob that is copied to the destination. The Get Blob Properties operation is billed as an All other operations operation. AzCopy uses the Copy Blob operation to copy blobs to another container which is billed as a write operation that is based on the destination tier.
Price factor Hot Cool Cold Price of a single list operation $0.0000055 $0.0000055 $0.0000180 Cost of listing operations (1 * operation price) $0.0000055 $0.0000055 $0.0000180 Price of a single other operations $0.00000044 $0.00000044 $0.00000044 Cost to get blob properties (2000 * operation price) $0.00088 $0.00088 $0.00088 Price of a single write operation $0.0000055 $0.00001 $0.000018 Cost to write (1000 * operation price) $0.0055 $0.01 $0.018 Total cost (listing + properties + write) $0.0064 $0.0109 $0.0189 Cost of copying blobs to another account in the same regionThis scenario is identical to the previous one except that you're also billed for data retrieval and for read operation that is based on the source tier.
Price factor Hot Cool Cold Total from previous section $0.0064 $0.0109 $0.0189 Price of a single read operation $0.00000044 $0.000001 $0.00001 Cost of read operations (1,000 * operation price) $0.00044 $0.001 $0.01 Price of data retrieval (per GiB) Free $0.01 $0.03 Cost of data retrieval 1000 * (5 * operation price) $0.00 $50.00 $150.00 Total cost (previous section + retrieval + read) $0.0068 $50.0119 $150.0290 Cost of copying blobs to an account located in another regionThis scenario is identical to the previous one except you're billed for network egress charges.
Price factor Hot Cool Cold Total cost from previous section $0.0068 $50.0119 $150.0290 Price of network egress (per GiB) $0.02 $0.02 $0.02 Total cost of network egress 1000 * (5 * price of egress) $100 $100 $100 Total cost (previous section + egress) $100.0068 $150.0119 $250.0290 The cost to synchronize changesWhen you run the azcopy sync command, you'll specify a source and destination endpoint. These endpoints can be either a Blob Service endpoint (blob.core.windows.net) or a Data Lake Storage endpoint (dfs.core.windows.net) endpoint.
Note
Blobs in the archive tier can be copied only to an online tier. Because all of these examples assume the same tier for source and destination, the archive tier is excluded from these tables.
Cost to synchronize a container with a local file systemIf you want to keep a container updated with changes to a local file system, then AzCopy performs the exact same tasks as described in the Cost of uploading to the Blob Service endpoint section in this article. Blobs are uploaded only if the last modified time of a local file is different than the last modified time of the blob in the container. Therefore, you're billed write transactions only for blobs that are uploaded.
If you want to keep a local file system updated with changes to a container, then AzCopy performs the exact same tasks as described in the Cost of downloading from the Blob Service endpoint section of this article. Blobs are downloaded only If the last modified time of a local blob is different than the last modified time of the blob in the container. Therefore, you're billed read transactions only for blobs that are downloaded.
Cost to synchronize containersIf you want to keep two containers synchronized, then AzCopy performs the exact same tasks as described in the The cost to copy between containers section in this article. A blob is copied only if the last modified time of a blob in the source container is different than the last modified time of a blob in the destination container. Therefore, you're billed write and read transactions only for blobs that are copied.
The azcopy sync command uses the List Blobs operation on both source and destination accounts when synchronizing containers that exist in separate accounts.
Summary of calculationsThe following table contains all of the estimates presented in this article. All estimates are based on transferring 1000 blobs that are each 5 GiB in size and use the sample prices listed in the next section.
Scenario Hot Cool Cold Archive Upload blobs (Blob Service endpoint) $3.53 $6.41 $11.54 $7.05 Upload blobs (Data Lake Storage endpoint) $9.16 $16.65 $29.98 $18.32 Download blobs (Blob Service endpoint) $0.001 $50.001 $150.011 N/A Download blobs (Data Lake Storage endpoint) $0.731 $51.666 $166.653 N/A Copy blobs $0.0064 $0.0109 $0.0189 N/A Copy blobs to another account $0.0068 $50.0119 $150.0290 N/A Copy blobs to an account in another region $100.0068 $150.0119 $250.0290 N/A Sample pricesThe following tables include sample (fictitious) prices for each request to the Blob Service endpoint (blob.core.windows.net).
The following tables assume that an account is configured for LRS redundancy.
Price factor Hot Cool Cold Archive Price of write operations (per 10,000) $0.055 $0.10 $0.18 $0.11 Price of read operations (per 10,000) $0.0044 $0.01 $0.10 $5.50 List and container operations (per 10,000) $0.055 $0.055 $0.18 $.055 All other operations (per 10,000) $0.0044 $0.0044 $0.0052 Not applicable Price of data retrieval (per GB) Free $0.01 $0.03 $.022 Price of Data storage first 50 TB (pay-as-you-go) $0.0208 $0.0115 $0.0045 $0.002 Price of Data storage next 450 TB (pay-as-you-go) $0.020 $0.0115 $0.0045 $0.002 Price of 100 TB (One-year reserved capacity) $1,747 $966 Not available $183 Price of 100 TB (Three-year reserved capacity) $1,406 $872 Not available $168 Network bandwidth between regions within North America (per GB) $0.02 $0.02 $0.02 $0.02 Price of high priority read operations (per 10,000) Not applicable Not applicable Not applicable $65.00 Price of high priority data retrieval (per GB) Not applicable Not applicable Not applicable $0.13The following table includes sample prices (fictitious) prices for each request to the Data Lake Storage endpoint (dfs.core.windows.net). For official prices, see Azure Data Lake Storage pricing.
The following tables assume that an account is configured for GRS redundancy.
Price factor Hot Cool Cold Archive Price of write operations (per 10,000) $0.1100 $0.20 $0.36 $0.21 Price of read operations (per 10,000) $0.0044 $0.01 $0.10 $5.50 List and container operations (per 10,000) $0.1100 $0.110 $0.110 $.110 All other operations (per 10,000) $0.0044 $0.0044 $0.0052 $.0044 Price of data retrieval (per GB) Free $0.01 $0.03 $.022 Price of Data storage first 50 TB (pay-as-you-go) $0.0458 $0.0230 $0.0081 $0.0030 Price of Data storage next 450 TB (pay-as-you-go) $0.0440 $0.0230 $0.0081 $0.0030 Price of 100 TB (One-year reserved capacity) $3,846 $1,932 Not available $273 Price of 100 TB (Three-year reserved capacity) $3,096 $1,743 Not available $252 Data transfer fees (per GB) $0.02 $0.02 $0.02 $0.02 Network bandwidth between regions within North America (per GB) $0.02 $0.02 $0.02 $0.02 Price of high priority read operations (per 10,000) Not applicable Not applicable Not applicable $65.00 Price of high priority data retrieval (per GB) Not applicable Not applicable Not applicable $0.13The following table includes sample prices (fictitious) prices for each request to the Data Lake Storage endpoint (dfs.core.windows.net). For official prices, see Azure Data Lake Storage pricing.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4