Skip to content

Commit 787a5e2

Browse files
committed
clarifying our pricing page
1 parent aa85ff5 commit 787a5e2

File tree

1 file changed

+20
-5
lines changed

1 file changed

+20
-5
lines changed

articles/application-gateway/understanding-pricing.md

Lines changed: 20 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,19 +41,22 @@ Application Gateway V2 and WAF V2 SKUs support autoscaling and guarantee high av
4141
Capacity Unit is the measure of capacity utilization for an Application Gateway across multiple parameters.
4242

4343
A single Capacity Unit consists of the following parameters:
44-
* 2500 Persistent connections
44+
* 2,500 Persistent connections
4545
* 2.22-Mbps throughput
4646
* 1 Compute Unit
4747

4848
The parameter with the highest utilization among these three parameters is used to calculate capacity units for billing purposes.
4949

50-
#### Capacity Unit related to Instance Count
50+
#### Capacity Units related to Instance Count
5151
<h4 id="instance-count"></h4>
5252

5353
You can also pre-provision resources by specifying the **Instance Count**. Each instance guarantees a minimum of 10 capacity units in terms of processing capability. The same instance could potentially support more than 10 capacity units for different traffic patterns depending upon the capacity unit parameters.
5454

5555
Manually defined scale and limits set for autoscaling (minimum or maximum) are set in terms of instance count. The manually set scale for instance count and the minimum instance count in autoscale config reserves 10 capacity units/instance. These reserved capacity units are billed as long as the application gateway is active regardless of the actual resource consumption. If actual consumption crosses the 10 capacity units/instance threshold, additional capacity units are billed under the variable component.
5656

57+
> [!NOTE]
58+
> An **Instance** is a physical deployment unit of Application Gateway. Users aren't billed directly for the number of instances, but rather for the capacity units reserved or consumed by the instances.
59+
5760
#### Total capacity units
5861

5962
Total capacity units are calculated based on the higher of the capacity units by utilization or by instance count.
@@ -69,6 +72,18 @@ Compute unit guidance:
6972

7073
The following table shows example prices using Application Gateway Standard v2 SKU. These prices are based on a snapshot of East US pricing and are for illustration purposes only.
7174

75+
> [!NOTE]
76+
> Compute units are an entirely different concept from capacity units. Compute units are a measure of compute capacity consumed, while capacity units are a measure of capacity utilization across multiple parameters. Compute units are one of three parameters used to calculate capacity units.
77+
78+
### How much traffic can an instance handle?
79+
80+
Each instance of Application Gateway Standard_v2 can handle the following traffic:
81+
* 25,000 persistent connections
82+
* 500-Mbps throughput
83+
* 10 compute units
84+
85+
Therefore, in cases where the dominant factor is either compute units or persistent connections, each instance can handle 10 capacity units. In cases where the dominant factor is throughput, each instance can handle approximately 225 capacity units. This data depends on the type of payload.
86+
7287
#### Fixed Costs (East US region pricing)
7388

7489
| V2 SKU | Costs ($/hr) |
@@ -116,7 +131,7 @@ Let’s assume you’ve provisioned a Standard_V2 Application Gateway with manua
116131

117132
Your Application Gateway costs using the pricing described previously are calculated as follows:
118133

119-
1 CU can handle 2.22 Mbps throughput.
134+
1 CU can handle 2.22-Mbps throughput.
120135

121136
CUs required to handle 88.8 Mbps = 88.8 / 2.22 = 40
122137

@@ -134,7 +149,7 @@ Variable Costs = $0.008 * ( 3 (Instance Units) * 10 (capacity units) + 10 (addit
134149
Total Costs = $179.58 + $233.6 = $413.18
135150

136151
However, if processing capacity equivalent to only say 7 additional CUs was available for use within the 3 reserved instances.
137-
In this scenario the Application Gateway resource is under scaled and could potentially lead to increase in latency or requests getting dropped.
152+
In this scenario, the Application Gateway resource is under scaled and could potentially lead to increase in latency or requests getting dropped.
138153

139154
Fixed Price = $0.246 * 730 (Hours) = $179.58
140155

@@ -401,7 +416,7 @@ You can view the amount of consumption for different parameters (compute unit, t
401416

402417
* Fixed Billable Capacity Units
403418

404-
The minimum number of capacity units kept provisioned as per the minimum instance count setting (one instance translates to 10 capacity units) in the Application Gateway configuration.
419+
The minimum number of capacity units kept provisioned as per the minimum instance count setting (one instance translates to a minimum of 10 capacity units) in the Application Gateway configuration.
405420

406421
* Estimated Billed Capacity units
407422

0 commit comments

Comments
 (0)