Skip to content

Commit b3087d3

Browse files
Merge pull request #262534 from vhorne/fw-perf
add clarification for scaling
2 parents 9916b1b + 29d6ee0 commit b3087d3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/firewall/firewall-performance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The following set of performance results demonstrates the maximal Azure Firewall
5454

5555
### Total throughput for initial firewall deployment
5656

57-
The following throughput numbers are for an Azure Firewall deployment before auto-scale (out of the box deployment). Azure Firewall gradually scales out when the average throughput and CPU consumption is at 60% or if the number of connections usage is at 80%. Scale out takes five to seven minutes. Azure Firewall gradually scales in when the average throughput or CPU consumption is below 20%.
57+
The following throughput numbers are for an Azure Firewall deployment before auto-scale (out of the box deployment). Azure Firewall gradually scales out when the average throughput and CPU consumption is at 60% or if the number of connections usage is at 80%. Scale out takes five to seven minutes. Azure Firewall gradually scales in when the average throughput, CPU consumption, or number of connections is below 20%.
5858

5959
When performance testing, ensure you test for at least 10 to 15 minutes, and start new connections to take advantage of newly created firewall nodes.
6060

0 commit comments

Comments
 (0)