You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/blobs/blob-storage-estimate-costs.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ See [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation
58
58
59
59
When you upload data, your client divides that data into blocks and uploads each block individually. Each block that is upload is billed as a _write_ operation. A final write operation is needed to assemble blocks into a blob that is stored in the account. The number of write operations required to upload a blob depends on the size of each block. **8 MiB** is the default block size for uploads to the Blob Service endpoint (`blob.core.windows.net`) and that size is configurable. **4 MiB** is the block size for uploads to the Data Lake Storage endpoint (`dfs.core.windows.net`) and that size isn't configurable. A smaller block size performs better because blocks can upload in parallel. However, the cost is higher because more write operations are required to upload a blob.
60
60
61
-
Using the [Sample prices](#sample-prices) that appear in this article, and assuming an **8-MiB** block size, the following table estimates the cost to upload **1000** blobs that are each **5 MiB** in size to the hot tier.
61
+
Using the [Sample prices](#sample-prices) that appear in this article, and assuming an **8-MiB** block size, the following table estimates the cost to upload **1000** blobs that are each **5 GiB** in size to the hot tier.
For more detailed examples, see [Estimate the cost to upload](azcopy-cost-estimation.md#the-cost-to-upload).
@@ -83,7 +83,7 @@ Using the [Sample prices](#sample-prices) that appear in this article, the follo
83
83
| Price of a single read operation (price / 10,000) | $0.000001 |
84
84
|**Cost of read operations (1000 * operation price)**|**$0.001**|
85
85
| Price of data retrieval (per GiB) | $0.01 |
86
-
|**Cost of data retrieval (5 * operation price)**|**$0.05**|
86
+
|**Cost of data retrieval (5 * price of data retrieval)**|**$0.05**|
87
87
|**Total cost (read + retrieval)**|**$0.051**|
88
88
89
89
Utilities such as AzCopy also use list operations and operations to obtain blob properties. As a proportion of the overall bill, these charges are relatively small. For examples, see [Estimate the cost to download](azcopy-cost-estimation.md#the-cost-to-download).
@@ -97,9 +97,9 @@ Using the [Sample prices](#sample-prices) that appear in this article, the follo
|**Cost to rename blob virtual directories (1000 * (1000 * price of a single operation)**|**$5.50**|**$10.00**|**$18.00**|
138
138
| Price of a single iterative write operation to the Data Lake Storage endpoint (price / 100) | $0.000715 | $0.000715 | $0.000715 |
139
-
|**Cost to rename Data Lake Storage directories (1000 * operation price)**|**$0.715**|**$0.715**|**0.715**|
139
+
|**Cost to rename Data Lake Storage directories (1000 * price of a single operation)**|**$0.715**|**$0.715**|**0.715**|
140
140
141
141
Based on these calculations, the cost to rename 1,000 directories in the hot tier that each contain 1,000 blobs differs by almost **$5.00**. For directories in the cold tier, the difference is over **$17**.
0 commit comments