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/files/how_to_estimate_the_cost_of_azure_files.md
+38-23Lines changed: 38 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,28 +8,35 @@ author: khdownie
8
8
ms.author: kendownie
9
9
ms.service: azure-file-storage
10
10
---
11
+
11
12
# How to Estimate the Cost of Azure Files
12
13
13
-
How to estimate the cost of Azure Files
14
14
In this article, we will demonstrate how to estimate the cost between Provisioned v1 and Provisioned v2 SSD billing model. We will provide a detailed breakdown of three scenarios used in the Provisioned v2 SSD release blog post.
15
-
Important
16
-
These prices are meant only as examples and should not be used to calculate your costs. For official prices, see the Azure File Storage pricing. For more information about how to choose the correct billing model, see Understand the billing model for Azure Files. We also encourage you to use Azure File Pricing calculator to perform the actual calculations.
15
+
16
+
>[!IMPORTANT]
17
+
>These prices are meant only as examples and should not be used to calculate your costs. For official prices, see the Azure File Storage pricing. For more information about how to choose the correct billing model, see Understand the billing model for Azure Files. We also encourage you to use Azure File Pricing calculator to perform the actual calculations.
18
+
17
19
For the following examples, we will be using pricing based on East US and LRS redundancy support. Provisioned v1 billing model is billed hourly in a monthly rate, where provisioned storage will be $0.16 per GiB. Provisioned v2 will be billed hourly in a hourly rate, provisioned storage will be $0.000137 per GiB per hour, Provisioned IOPS at $0.000037 per IOPS per hour, and provisioned throughput at $0.000054 per MiB per sec per hour. For the easy of calculations, we will assume all month have 730 hours. If you want to calculate the exact price, replace the hours with 24 × days in the specific month.
18
-
Comparison using defaults IOPS and throughputs:
20
+
21
+
### Comparison using defaults IOPS and throughputs:
19
22
For this scenario, we are using the recommended IOPS and throughput based on our capacity request:
| Total cost | $1,638.40/month | $1,341.09/month |
29
33
30
34
100 – ($1,341.09 / $1,638.40 × 100) = 18.15%
35
+
31
36
With the exact same provisioning size, IOPS, and throughput, using the Pv2 billing model saves around 18% monthly on the total cost of ownership for the file share.
32
-
Comparison of relational database workload
37
+
38
+
### Comparison of relational database workload
39
+
33
40
Let us assume we are making a price comparison in the following relational database workload deployment.
34
41
• 4,096 GiB in capacity
35
42
• 20,000 IOPS
@@ -39,15 +46,20 @@ If we are using the provisioned v1 billing model, we need to reverse calculate o
39
46
• To meet throughput requirements, we will need (1536-100)/ (0.04+0.06) = 14,360 GiB
40
47
Learn more about the equation at Understand the billing model for Azure Files.
41
48
To meet both requirements, in Provisioned v1, we need to provision 17,000 GiB to meet all three criteria.
0 commit comments