Instance Size
Instance Size is the gateway instance size.
When selecting the gateway instance size, use the following guidelines of IPsec performance based on IPERF tests conducted between two gateways of the same size:
AWS Performance Numbers:
AWS Instance Size | Expected Throughput |
---|---|
T2 series |
Not guaranteed; it can burst up to 130Mbps |
c5.2xlarge, c5.4xlarge |
2Gbps - 2.5Gbps |
c5n.4xlarge |
25Gbps (with High Performance Encryption (HPE) Mode) |
c5n.9xlarge |
70Gbps (with HPE Mode) |
c5n.18xlarge |
70Gbps (with HPE Mode) |
Azure Performance Numbers (without High Performance Encryption Mode):
Azure Instance Size | Expected Throughput |
---|---|
B series |
Not guaranteed; it can burst up to 260Mbps |
D/Ds series |
480Mbps - 1.2Gbps |
F Series |
approximately 450Mbps - 1.2Gbps |
GCP Performance Numbers (without High Performance Encryption Mode):
GCP Instance Size | Expected Throughput |
---|---|
n1-standard-1, n1-standard-2, n1-highcpu-2 |
1.0 - 1.2 Gbps |
n1-standard-4, n1-highcpu-2 |
2.3 - 2.5 Gbps |
OCI Expected Throughput Numbers:
OCI Instance Shape | Throughput with Active Mesh | Throughput without Active Mesh |
---|---|---|
VM.Standard2.2 or larger |
1.8G |
900 Mbps |
With OCI you can choose a flexible shape to modify the Oracle CPU (OCPU) and memory configurations of your shape after it is deployed.
OCI Flex Shape | OCPU and RAM |
---|---|
FLEX4.16 |
E3 4 OCPU 8G RAM |
FLEX8.32 |
E3 8 OCPU 32G RAM |
FLEX16.32 |
E3 16 OCPU 32G RAM |
If you need IPsec performance beyond 2Gbps, refer to ActiveMesh HPE Performance Benchmark. |
Gateway Resize
You can change gateway instance size, if needed, to change gateway throughput. The gateway instance will restart with a different instance size.
If you use Availability Set when launching Azure gateways, different classes of VM sizes can be resized interchangeably.
See the Resizing a Gateway document.
To change gateway instance size, see Changing Gateway Instance Size