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/azure-netapp-files/azure-netapp-files-cost-model.md
+22-21Lines changed: 22 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,57 +26,58 @@ For cost model specific to cross-region replication, see [Cost model for cross-r
26
26
27
27
Azure NetApp Files is billed on provisioned storage capacity, which is allocated by creating capacity pools. Capacity pools are billed monthly based on a set cost per allocated GiB per hour. Capacity pool allocation is measured hourly.
28
28
29
-
Capacity pools must be at least 4 TiB and can be changed in 1 TiB intervals. Capacity pools contain volumes that range in size from a minimum of 100 GiB to a maximum of 100 TiB. Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](.snapshots-introduction.md) for details.
29
+
Capacity pools must be at least 4 TiB and can be increased or decreased in 1 TiB intervals. Capacity pools contain volumes that range in size from a minimum of 100 GiB to a maximum of 100 TiB. Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](.snapshots-introduction.md) for details.
30
30
31
-
## Pricing examples
31
+
### Pricing examples
32
+
33
+
This section shows you examples to help you understand the Azure NetApp Files cost model.
32
34
33
35
#### Example 1: One month cost with static versus dynamic capacity pool provisioning
34
36
35
-
If your capacity pool size requirements fluctuate (e.g. because of variable capacity or performance needs), you may want to resize your volumes and capacity pools dynamically in order to balance cost with capacity and performance needs.
37
+
If your capacity pool size requirements fluctuate (for example, because of variable capacity or performance needs), you might want to resize your volumes and capacity pools dynamically in order to balance cost with capacity and performance needs.
36
38
37
-
Consider a scenario where you are using the standard premium capacity 24 hours (1 day) at 10 TiB, 96 hours (4 days) at 24 TiB, four times at 6 hours (1 day) at 5 TiB, 480 hours (20 days) at 6 TiB, and the month’s remaining hours at 0 TiB, a dynamic cloud consumption deployment profile looks different from a static on-premise consumption profile:
39
+
Consider a scenario where you are using the Premium capacity 24 hours (1 day) at 10 TiB, 96 hours (4 days) at 24 TiB, four times at 6 hours (1 day) at 5 TiB, 480 hours (20 days) at 6 TiB, and the month’s remaining hours at 0 TiB, a dynamic cloud consumption deployment profile looks different from a traditional static on-premise consumption profile:
38
40
39
41
40
42
41
-
When costs are billed at $0.000403 per GiB/hour (pricing varies depending on region) the monthly cost breakdown looks like:
43
+
When costs are billed at $0.000403 per GiB/hour (pricing varies depending on the region), the monthly cost breakdown looks like the following:
42
44
43
-
*Static provisioning on premium (peak capacity/performance)*
45
+
*Static provisioning on Premium (peak capacity/performance)*
44
46
45
47
* 24 TiB x 720 hours x $0.000403 per GiB/hour = $7,130.97 per month ($237.70 per day)
46
48
47
49
*Dynamic provisioning using dynamic service level change*
48
50
49
-
* 24 TiB x 384 hours x $0.000202 per GiB/hour = $1,901.31
50
-
* 24 TiB x 120 hours x $0.000403 per GiB/hour = $1,188.50
51
-
* 24 TiB x 168 hours x $0.000538 per GiB/hour = $2,221.28
52
-
* 24 TiB x 48 hours x $0.000202 per GiB/hour = $238.29
53
-
* Total = $5,554.37
51
+
* 10TiB x 24 hours x $0.000403 per GiB/hour = $99.04
52
+
* 24TiB x 96 hours x $0.000403 per GiB/hour = $950.80
53
+
* 6TiB x 480 hours x $0.000403 per GiB/hour = **$1,188.50**
54
+
* Total = $2,238.33
54
55
55
-
56
+
56
57
57
58
This constitutes a monthly savings of $4892.64 compared to static provisioning.
58
59
59
60
#### Example 2: One month cost with and without dynamic service level change
60
61
61
-
If your capacity pool size requirements remain the same but performance requirements fluctuate, you may want to change the service level of a volume for Azure NetApp Files dynamically. This allows you to provision and deprovision capacity pools of different types throughout the month, providing just-in-time performance, lowering costs during periods where perfomance is not needed.
62
+
If your capacity pool size requirements remain the same but performance requirements fluctuate, you might want to consider [dynamically changing the service level of a volume for Azure NetApp Files](dynamic-change-volume-service-level.md). This approach allows you to provision and deprovision capacity pools of different types throughout the month, providing just-in-time performance, and lowering costs during periods where performance is not needed.
62
63
63
-
Consider a scenario where the capacity requirement is a constant 24 TiB but your performance needs fluctuate between 384 hours (16 days) of standard tier, 120 hours (5 days) of premium tier, 168 hours (7 days) of ultra tier, and then back to 48 hours (2 days) of standard tier performance. In this case, a dyanmic cloud consumption deployment profile looks different from a static on-premise consumption profile:
64
+
Consider a scenario where the capacity requirement is a constant 24 TiB but your performance needs fluctuate between 384 hours (16 days) of Standard service level, 120 hours (5 days) of Premium service level, 168 hours (7 days) of Ultra service level, and then back to 48 hours (2 days) of standard service level performance. In this case, a dynamic cloud consumption deployment profile looks different compared to a traditional static on-premise consumption profile:
64
65
65
66
66
67
67
-
In this case, when costs are billed at $0.000202 per GiB/hour (standard), $0.000403 per GiB/hour (premium) and $0.000538 per GiB/hour (ultra) respectively (pricing depending on region) the monthly cost breakdown looks like:
68
+
In this case, when costs are billed at $0.000202 per GiB/hour (Standard), $0.000403 per GiB/hour (Premium) and $0.000538 per GiB/hour (Ultra) respectively (pricing depending on region) the monthly cost breakdown looks like the following:
68
69
69
-
*Static provisioning on ultra tier (peak performance)*
70
+
*Static provisioning on Ultra service level (peak performance)*
70
71
71
72
* 24TiB x 720 hours x $0.000538 per GiB/hour = $9,519.76 per month ($317.33 per day)
72
73
73
74
*Dynamic provisioning using dynamic service level change*
74
75
75
-
24TiB x 384 hours x $0.000202 per GiB/hour = $1,901.31
76
-
24TiB x 120 hours x $0.000403 per GiB/hour = $1,188.50
77
-
24TiB x 168 hours x $0.000538 per GiB/hour = $2,221.28
78
-
24TiB x 48 hours x $0.000202 per GiB/hour = $238.29
79
-
Total = $5,554.37
76
+
* 24 TiB x 384 hours x $0.000202 per GiB/hour = $1,901.31
77
+
* 24 TiB x 120 hours x $0.000403 per GiB/hour = $1,188.50
78
+
* 24 TiB x 168 hours x $0.000538 per GiB/hour = $2,221.28
79
+
* 24 TiB x 48 hours x $0.000202 per GiB/hour = **$238.29**
80
+
*Total = $5,554.37
80
81
81
82
0 commit comments