Latest Posts



Translate

Total Pageviews

Friday, 2 May 2014

Differences between Compact, Large and X-Large Edge Gateway appliances?

The vCloud Networking and Security Edge Gateway is available in three different sizes: Compact, Large, and X-Large. As part of the Edge Gateway deployment, we need to select the appliance size in the wizard as shown below.

 
The three different Edge Gateway appliances consume different resources and offer different performance levels. The resources used by three different Edge Gateway appliances and their performance levels based on VMware internal testing are posted in the vCloud Networking and Security 5.1 Edge configuration limits and throughput KB article.
As indicated in the KB article, Large appliance offers higher throughput compared to Compact appliance in terms of firewall performance, number of concurrent sessions, and IPSec VPN throughput.
 Edge (Compact)Edge (Large)
vCPU12
Memory256 MB1 GB
Firewall Performance (Gbps)39.7
Concurrent Sessions64,0001,000,000
IPSec VPN throughput (Gbps) – H/W acceleration via AESNI0.92
Use of Large or X-Large appliance recommended for using Edge Gateway load balancing service. X-Large appliance uses much higher memory and allows higher number of concurrent load balancer connections than Large appliance. The X-large Edge Gateway is not currently supported with vCloud Director 5.1.  As the picture above shows, the X-Large deployment model has some limitations, such as a lack of SSL VPN support.
 Edge (Large)Edge (X-Large)
vCPU22
Memory1 GB8 GB
Load balancer throughput – L7 Proxy Mode (Gbps)2.23
Load balancer connections / sec – L7 Proxy Mode46,00050,000
Load balancer concurrent connections – L7 Proxy Mode8,00060,000
Another cool feature offered with Edge Gateway deployment is we can start with one appliance and move to a different appliance at a later time. For example, we can deploy Edge Gateway Compact appliance and later upgrade to Large or X-Large with a click of a button as shown below.In summary, choose the Edge Gateway appliance that suits your environment based on the resources consumed and the performance levels offered.
Info taken from blogs.vmware.com