Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This sample estimates the cost to upload and download data from multiple Azure regions.
Important
This estimate is based on these sample prices. Sample prices shouldn't be used to calculate your production costs. To find official prices, see Find the unit price for each meter.
Scenario
Your company plans to distribute a new client application to users located in multiple Azure regions across the continent. This application is used to upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
The storage account is located in the West US region, is configured for Geo-redundant storage (GRS) and doesn't have hierarchical namespaces enabled.
Costs
The following table describes each cost.
| Cost | Description |
|---|---|
| Cost to write | During this quarter, clients upload an estimated 50,000 log files (roughly 1 GB each in size). Clients are configured to upload those log files in 8-MiB blocks. Each block is billed as a write operation with one additional operation to commit those blocks. A smaller block size is performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
| Cost of replication | Because the account is configured for geo-redundant storage, all blobs are replicated to a secondary region. This replication process adds a data transfer fee per GB replicated. |
| Cost to read | Any blob that is downloaded for diagnostic analysis is billed as a read operation. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that 75% of client applications aren't located in the same region as the storage account. Therefore, blobs downloaded by those clients incur a network bandwidth fee. |
Estimate
Based on these sample prices, the following table shows how each cost component is calculated.
| Cost | Cost factor | Calculation | Value |
|---|---|---|---|
| Cost to write | PutBlock operations per blob | 1 GiB / 8-MiB block | 155 |
| PutBlockList operations per blob | 1 per blob | 1 | |
| Price of a write operation on the hot tier | $0.000021 | ||
| Cost to upload log files |
(50,000 blobs * 156) * $0.000021 | $163.80 | |
| Cost of replication | Price of data transfer (per GB) | $0.02 | |
| Cost to replicate |
50,000 GB * $0.02 | $1,000.00 | |
| Cost to read | Number of read operations | 50,000 / 2 | 25,000 |
| Price a read operation on the hot tier | $0.00440 | ||
| Cost of read operations |
25,000 GB * $0.00440 | $110.00 | |
| Number of blobs downloaded from other regions | 25,000 * 75% | 1875 | |
| Network bandwidth fee | 1875 * $0.02 | $375.00 | |
| Cost to read |
$110 + $375 | $485 | |
| Total cost | $163.80 + $1,000 + $485 | $1,648.80 |
Tip
This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include cost of data storage which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using Azure pricing calculator.