The Compression tab permits one to view or edit the application profile’s compression settings.

To configure compression:


  1. Navigate to Templates > Application profile
  2. Click Create to create a new profile or use the existing application profile as required.
  3. Select the Compression tab and enable to feature if it is not enabled.
  4. Select the compression mode as desired.

    The Auto and Custom mode is described in the later section. The compression percentage achieved can be viewed using the Client Logs tab of the virtual service. This may require enabling full client logs on the virtual service’s Analytics tab to log some or all client requests. The logs will include a field showing the compression percentage with each HTTP response.

    To specify compression settings, perform the following:

    • Check the Compression checkbox to enable compression. You may only change compression settings after enabling this feature.

    • Select either Auto or Custom, which enables different levels of compression for different clients. For instance, filters can be created to provide aggressive compression levels for slow mobile clients while disabling compression for fast clients from the local intranet. Auto is recommended, to dynamically tune the settings based on clients and available Service Engine CPU resources.

      • Auto mode enables NSX Advanced Load Balancer to determine the optimal settings.


      By default, the Compression Mode is Auto. The content compression depends on the client’s RTT, as mentioned below:

      • RTT less than 10ms, no compression

      • RTT 10 to 200ms, normal compression

      • RTT above 200ms, aggressive compression

      • Custom mode allows the creation of custom filters that provide more granular control over who should receive what level of compression.

    • Compressible Content Types determine which HTTP Content-Types are eligible to be compressed. This field points to a String Group which contains the compressible type list.

    • Remove Accept Encoding Header removes the Accept-Encoding header, which is sent by HTTP 1.1 clients to indicate they can accept compressed content. Removing the header from the request prior to sending the request to the server allows NSX Advanced Load Balancer to ensure the server will not compress the responses. Only NSX Advanced Load Balancer will perform compression.