To extract maximum performance from your sized FortiGate-VM instance, apply the following optimization techniques within Azure and FortiOS. Enable DPDK (Data Plane Development Kit)
For example, an Standard_F4sv2 VM offers a maximum of 4,000 Mbps (4 Gbps) of Azure network bandwidth. No matter how efficiently FortiOS processes packets, the VM cannot exceed this cloud-enforced ceiling. Accelerated Networking (SR-IOV)
Choosing the right FortiGate VM size in Azure is critical for balancing security performance with cloud costs. Because Azure instances have specific limits on CPU, RAM, and network throughput, your selection directly impacts how much traffic your firewall can inspect. Determining Your Throughput Requirements fortigate vm sizing azure
Based on the factors mentioned earlier, here are some general guidelines for sizing a FortiGate VM in Azure:
Offers flexibility to choose specific vCPU/RAM ratios. To extract maximum performance from your sized FortiGate-VM
FortiOS utilizes a multi-threaded architecture to process traffic. However, Azure enforces strict CPU scheduling across shared hardware.
Throughput figures are estimates. Actual performance depends on packet size, security profile mix, and Azure region. Actual performance depends on packet size
Look for asymmetric load where Core 0 or Core 1 hits 100% while others sit idle (indicates lack of RSS optimization or single-stream elephant flows).
Requires sizing the active node to handle 100% of the peak workload. The passive node sits idle but must match the active node's size exactly.