Memory Utilization in Resilient Protectors

The 10.0.x Protectors support a Resilient Deployment architecture, which uses dynamic memory allocation to store the resilient packages downloaded from the ESA or the upstream server. In comparison, the protectors prior to version 10.0.x support a PEP Server based architecture, which uses fixed memory allocation to store the policies downloaded from the ESA. As a result, the Resilient Deployment architecture offers a memory efficient solution as compared to the PEP Server architecture.

The new Resilient Deployment architecture offers the following advantages over the PEP Server architecture:

• Scalability:
  • Easy to scale the protectors by increasing the hardware.
  • No limits on the policy size.
• Lower costs: Less network and memory requirements thereby reducing the hardware costs.
• Secure: Enables configuration to only store policy in process memory.
• Improved performance: Takes less time in distributing the resilient packages.

Memory Consumption during Policy Enforcement

The following example shows how much memory is consumed by an 10.0.x Protector when a policy is successfully loaded in heap memory. An application log is generated specifying the memory used.

{"additional_info":{"description":"Policy successfully loaded","memoryUsed":"13"}}

In this example, the memory used is 13 MB. This application log is then sent to Insight, where you can view the memory utilization for all the protectors.

For more information about Protegrity Dashboards, refer to the section Viewing the dashboards.

For more information about application logs, refer to the section Application Logs.

The following table shows how the number of data elements in combination with number of users affect the memory consumption.

The average length of user names is 16 characters.

For more information about capacity planning, contact Protegrity Support.