NSX Advanced Load Balancer Performance Datasheet

Overview

The purpose of this guide is to provide general information about the data path performance of NSX Advanced Load Balancer (Avi Networks) based on configuration examples and different measured metrics from lab tests.

This guide does not include a formal performance study and the outcome can vary if different configurations are used, but the information is valuable for anyone to understand Avi’s performance.

The tests were performed with NSX Advanced Load Balancer version 20.1.6 with full access vCenter cloud. The information found within this document remains valid through the current versions and for current operating versions.

Avi Performance on vCenter Cloud

Notes:

1. Tested on Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz, supermicro, 32 CPUs x 2.4 GHz, 256 GB memory with NSX Advanced Load Balancer 20.1.6.

2. The Service Engines were deployed on VMware vCenter, using Avi’s VMware Cloud Connector and Write Access automation.

3. Core = Service Engine VM Core (Service Cores)

4. Throughput measurements are virtual service throughput, calculated by aggregating the client-facing traffic only. Total throughput on the Service Engine is approximately double.

5. SSL Tests were performed with:

   • EC (SECP2 56R1) and RSA (2048 Bits)

   • Cipher used:

     • EC — TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

     • RSA — TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

   • PFS enabled, TLS version 1.2

6. The above data is per Service Engine VM. Avi’s L3-based Active-Active scaling capability allows customers to scale out based on application requirements on-demand.

7. The performed tests are done with CPU limit set to ‘unlimited’ for Service Engine VM. This is the default setting for bringing up the Service Engine VM.

8. *Open Connections capacity (also known as Concurrent Connections) can be increased by adding more memory to the Service Engine.

9. **L4 Throughput on SEs with 4 core or more tested with 2 dispatcher cores.

10. SE dispatcher/ proxy cores configuration:

    • 1 Core and 2 Core SE — Dedicated dispatcher set to False
    • 4 Core and 6 Core SE — Dedicated dispatcher set to True
    • 4 Core SE — 1 dispatcher core, 3 proxy cores
      • 2 Dispatcher and 2 proxy cores for L4-throughput tests
    • 6 Core SE— 2 Dispatcher cores, 4 proxy cores

Document Revision History