Manual Chapter : Caching Objects in a VIPRION Cluster

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 11.6.4, 11.6.3, 11.6.2, 11.6.1
Manual Chapter

Caching Objects in a VIPRION Cluster

Overview: Acceleration in a cluster

A VIPRION® system provides you with the ability to cache objects either for a policy node in a cluster or on a single cluster member. Typically, caching objects in a cluster achieves optimum acceleration for large, static objects. Comparatively, caching objects on a single cluster member achieves optimum acceleration for small, dynamic objects.

Caching objects in a cluster or cluster member

You can cache objects for a policy node in a cluster or on a single cluster member, optimizing acceleration for specific objects by policy node.

  1. On the Main tab, click Acceleration > Web Application > Policies .
    The Policies screen displays a list of existing acceleration policies.
  2. Click the name of a user-defined acceleration policy.
  3. Click a node in the Policy Tree.
  4. From the Matching Rules menu, choose Acceleration Rules.
  5. On the menu bar, click Responses Cached.
  6. Optional: For the Object Min Size setting, clear the Use Profile Setting check box, and type the minimum object size (in bytes) to cache, overriding the Web Acceleration profile setting.
  7. Optional: For the Object Max Size setting, clear the Use Profile Setting check box, and type the maximum object size (in bytes) to cache, overriding the Web Acceleration profile setting.
  8. From the Content Coherency list, select a cache coherency setting.
    Option Description
    Cluster (default) Provides optimum acceleration for large, static objects.
    Blade Provides optimum acceleration for small, dynamic objects.
  9. Click Save.
  10. Publish the acceleration policy.
    1. Click Publish.
    2. In the Comment field, type a description.
    3. Click Publish Now.
Objects for a policy node are cached in a cluster or on a single cluster member.