How well your Identity Manager solution performs can depend on the following deployment-specific settings:
Resource configuration
How many resources are connecting
What type of resources are connecting
How attributes are mapped on the resources
Exact resource version
Network topology
Number (and distribution) of domain controllers
Number of installed Identity Manager Gateways
Number of concurrent settings
Number of concurrent processes (running workflows)
Number of concurrent users
Number of concurrent Identity Manager administrators
Total number of users under management
When you are trying to debug performance problems, start by analyzing and describing the problem. Ask yourself the following questions:
Where do you see the performance issue? In reconciliation, workflows, custom workflows, GUI page loading, provisioning, Access Review?
Are you CPU bound, memory bound, resource bound, or network bound?
Have you examined your configuration (hardware, network, parameters, and so forth) for problems?
Have you recently changed anything in your deployment environment?
Have you tried profiling troublesome resources natively to see if the problem is on the resource side and not with Identity Manager?
What size are the views?
Are you provisioning to several resources?
Are resources on slow networks connecting to Identity Manager?
Are you running additional applications on the server with Identity Manager?
Do your organizations have a Rule-Driven Members rule?
Have you run a series of thread dumps to see if there is a consistent pattern?
Looking at just a single thread dump can be misleading.
Have you recently turned on tracing?
Have you checked your JVM garbage collection?
Have you added organizations that are adding load to memory management?