Merge pull request #293938 from MekaylaMoore/patch-12

Update expressroute-gateway-performance-include.md

Author: JillGrant615

includes/expressroute-gateway-performance-include.md

@@ -10,32 +10,23 @@
  ms.custom: include file
 ---
 
-The following tables provide an overview of the different types of gateways, their respective limitations, and their expected performance metrics. These numbers are derived from the following testing conditions and represent the maximum support limits. Actual performance might vary, depending on how closely traffic replicates these testing conditions.
+The following tables provide an overview of the different types of gateways, their respective limitations, and their expected performance metrics.
 
-#### Testing conditions
 
-| Gateway SKU | Traffic sent from on-premises | Number of routes advertised by gateway | Number of routes learned by gateway |
-|--|--|--|--|
-| **Standard/ERGw1Az** | 1 Gbps | 500 | 4,000 |
-| **High Performance/ERGw2Az** | 2 Gbps | 500 | 9,500 |
-| **Ultra Performance/ErGw3Az** | 10 Gbps | 500 | 9,500 |
-| **ErGwScale (per scale unit)** | 1 Gbps | 500 | 4,000 |
-
-> [!NOTE]
-> ExpressRoute can facilitate up to 11,000 routes that span virtual network address spaces, on-premises networks, and any relevant virtual network peering connections. To ensure stability of your ExpressRoute connection, refrain from advertising more than 11,000 routes to ExpressRoute.
-
-#### Performance results
+#### Maximum supported limits
 
 This table applies to both the Azure Resource Manager and classic deployment models.
 
-| Gateway SKU | Megabits per second | Packets per second | Supported number of VMs in the virtual network <sup>1</sup> | Flow count limit |
-|--|--|--|--|--|
-| **Standard/ERGw1Az** | 1,000 | 100,000 | 2,000 | 200,000 |
-| **High Performance/ERGw2Az** | 2,000 | 200,000 | 4,500 | 400,000 |
-| **Ultra Performance/ErGw3Az** | 10,000 | 1,000,000 | 11,000 | 1,000,000 |
-| **ErGwScale (per scale unit)** | 1,000 | 100,000 | 2,000 | 100,000 per scale unit |
+| Gateway SKU | Megabits per second | Packets per second | Supported number of VMs in the virtual network <sup>1</sup> | Flow count limit | Number of routes learned by gateway |
+|--|--|--|--|--|--|
+| **Standard/ERGw1Az** | 1,000 | 100,000 | 2,000 | 200,000 | 4,000 |
+| **High Performance/ERGw2Az** | 2,000 | 200,000 | 4,500 | 400,000 | 9,500 |
+| **Ultra Performance/ErGw3Az** | 10,000 | 1,000,000 | 11,000 | 1,000,000 | 9,500 |
+| **ErGwScale (per scale unit 1-40)** | 1,000 per scale unit | 100,000 per scale unit | 2,000 per scale unit | 100,000 per scale unit | 60,000 total per gateway
 
 <sup>1</sup> The values in the table are estimates and vary depending on the CPU utilization of the gateway. If the CPU utilization is high and the number of supported VMs is exceeded, the gateway will start to drop packets.
+> [!NOTE]
+> ExpressRoute can facilitate up to 11,000 routes that span virtual network address spaces, on-premises networks, and any relevant virtual network peering connections. To ensure stability of your ExpressRoute connection, refrain from advertising more than 11,000 routes to ExpressRoute. The maximum number of routes advertised by gateway is 1,000 routes.
 
 > [!IMPORTANT]
 > * Application performance depends on multiple factors, such as end-to-end latency and the number of traffic flows that the application opens. The numbers in the table represent the upper limit that the application can theoretically achieve in an ideal environment. Additionally, we perform routine host and OS maintenance on the ExpressRoute virtual network gateway, to maintain reliability of the service. During a maintenance period, the control plane and data path capacity of the gateway is reduced.