VM-Series on Microsoft Azure Performance and Capacity
Performance
—Many factors, such
as the virtual machine size on Microsoft Azure, maximum packets
per second supported, and the number of cores used, can affect VM-Series
performance. In addition to those noted, the performance and capacities
listed in the following table have been generated under controlled
lab conditions, using the recommended Azure virtual machine size,
and configured with Azure Accelerated Networking using SR-IOV and
DPDK under the following test conditions:
Firewall throughput and IPsec VPN are measured with App-ID™ and
User-ID™ technology features enabled, utilizing 64 KB HTTP transactions
Threat Prevention throughput is measured with App-ID, User-ID,
IPS, antivirus, and anti-spyware features enabled, utilizing 64K
HTTP transactions.
IPsec VPN performance is tested between two VM-Series in
the same region. The performance will depend on Azure VM size and
network topology, that is, whether connecting on-premises hardware
to VM-Series on Azure; from VM-Series on an Azure VNet to an Azure
VPN Gateway in another VNet; or VM-Series to VM-Series between regions.
New sessions per second are measured with 1 byte HTTP transactions.
Model
VM-50 / VM-50 Lite*
VM-100
VM-300
VM-500
VM-700
Azure instance size tested (recommended)
N/A
DS3_v2
DS3_v2
DS4_v2
DS5_v2
Firewall throughput (App-ID enabled)
N/A
1.5 Gbps
2.2 Gbps
2.5 Gbps **
2.5 Gbps**
Threat Prevention throughput
N/A
0.8 Gbps
1.9 Gbps
2.5 Gbps**
2.5 Gbps**
IPsec VPN throughput
N/A
0.5 Gbps
0.9 Gbps
1.3 Gbps
1.63 Gbps
*The VM-50 and VM-50 Lite are not supported on Azure.
— For a complete listing of all VM-Series features
and capacities, please use the firewall comparison tool.
VM-Series capacities specified in the page are not specific
to Azure environments. For example, Azure Network Flow limits will
limit your VM-Series session capacities in Azure.
Palo Alto Networks recommends additional testing within your
environment to ensure that your performance and capacity requirements
are met.
