Java Heap Size Capacity Planning - Identity Manager
search cancel

Java Heap Size Capacity Planning - Identity Manager

book

Article ID: 140353

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

Determining the optimal Java Heap size for Identity Manager application servers requires careful analysis of specific environment usage and load profiles. There is no single universal formula for calculating heap requirements; this article details the factors that influence memory consumption and provides a recommended methodology for determining your optimal configuration.

Environment

Identity Manager 14.5 & 15

Cause

Heap size requirements are dynamic and depend on the specific deployment architecture, such as task volume, concurrent user sessions, report generation frequency, and the complexity of policy configurations. Because every Identity Manager environment is unique, Java heap must be determined through performance testing in a representative staging environment rather than a fixed calculation.

Resolution

To determine the appropriate heap size for your Identity Manager environment, perform the following steps:

  1. Analyze Usage Factors: Evaluate your environment based on the following high-impact activities:

    • User Tasks: Number of daily Create, Modify, Terminate, and Re-Hire user tasks.
    • Access Requests: Volume of roles, groups, and attribute requests.
    • Bulk Operations: Number of daily bulk tasks and HR feed loader tasks.
    • Audit & Reporting: Total daily reports generated and audit data persistence settings.
    • Policy Complexity: Number of Policy Xpress policies and roles managed.
  2. Performance Testing (Recommended):

    • Configure your test environment using the recommendations found in the [Identity Manager Performance Tuning Guide].
    • Simulate your peak production load within your test environment.
    • Monitor JVM performance using tools such as VisualVM, JConsole, or by analyzing Garbage Collection (GC) logs.
    • Adjust heap parameters incrementally based on load test results until you reach a stable state that meets performance SLAs.
  3. Engage Professional Services: If you require a detailed analysis of your specific use case, contact your Broadcom Account Team to engage a partner for an environment and usage review.

Additional Information

For further information about performance, see documentation Performance Tuning - 14.5 or Performance Tuning - v15

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.