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
+8-17Lines changed: 8 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,16 +58,15 @@ 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 GiB** in size to the hot tier. The calculation for the "Cost of write operations" uses the price of a single operation instead of the price for 10,000 operations on the Azure Pricing Calculator.
62
-
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).
@@ -86,8 +85,6 @@ Using the [Sample prices](#sample-prices) that appear in this article, the follo
86
85
|**Cost of data retrieval (5 * data retrieval's price per GiB)**|**$0.05**|
87
86
|**Total cost (read + retrieval)**|**$0.051**|
88
87
89
-
The calculation for the "Cost of read operations" uses the price of a single, read or write, operation instead of the price for 10,000 operations on the Azure Pricing Calculator.
90
-
91
88
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).
92
89
93
90
#### The cost to copy between containers
@@ -99,13 +96,11 @@ Using the [Sample prices](#sample-prices) that appear in this article, the follo
The calculations for the 'Cost of read operations' and 'Cost of write operations' use the price of a single read or write operation instead of the price for 10,000 operations on the Azure Pricing Calculator.
108
-
109
104
For a complete example, see [Estimate the cost to copy between containers](azcopy-cost-estimation.md#the-cost-to-copy-between-containers).
110
105
111
106
## The cost to rename a blob
@@ -121,11 +116,9 @@ Using the [Sample prices](#sample-prices) that appear in this article, the follo
| Price of a single write operation to the Blob Service endpoint (price / 10,000) | $0.0000055 | $0.00001 | $0.000018 |
124
-
|**Cost to rename blob virtual directories (1000 * operation price)**|**$0.0055**|**$0.01**|**$.018**|
119
+
|**Cost to rename blob virtual directories (1000 * price of a single operation)**|**$0.0055**|**$0.01**|**$.018**|
125
120
| Price of a single iterative write operation to the Data Lake Storage endpoint (price / 100) | $0.000715 | $0.000715 | $0.000715 |
126
-
|**Cost to rename Data Lake Storage directories (1000 * operation price)**|**$0.715**|**$0.715**|**$0.715**|
127
-
128
-
The calculations for the "Cost to rename" uses the price of a single operation instead of the price for 10,000 operations on the Azure Pricing Calculator.
121
+
|**Cost to rename Data Lake Storage directories (1000 * price of a single operation)**|**$0.715**|**$0.715**|**$0.715**|
129
122
130
123
Based on these calculations, the cost to rename 1,000 blobs in the hot tier differs by **70** cents.
131
124
@@ -140,11 +133,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**|
144
137
| Price of a single iterative write operation to the Data Lake Storage endpoint (price / 100) | $0.000715 | $0.000715 | $0.000715 |
145
-
|**Cost to rename Data Lake Storage directories (1000 * operation price)**|**$0.715**|**$0.715**|**0.715**|
146
-
147
-
The calculations for the "Cost to rename" uses the price of a single operation instead of the price for 10,000 operations on the Azure Pricing Calculator.
138
+
|**Cost to rename Data Lake Storage directories (1000 * price of a single operation)**|**$0.715**|**$0.715**|**0.715**|
148
139
149
140
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