Tuning Instances
This section covers key AM tunings to ensure smoothly performing access and federation management services, and to maximize throughput while minimizing response times.
Note
The recommendations provided here are guidelines for your testing rather than hard and fast rules for every situation. Said another way, the fact that a given setting is configurable implies that no one setting is right in all circumstances.
The extent to which performance tuning advice applies depends to a large extent on your requirements, on your workload, and on what resources you have available. Test suggestions before rolling them out into production.
The suggestions in this section pertain to AM deployments with the following characteristics:
The deployment has a dedicated DS server for the Core Token Service. The host running this directory server is a high-end server with a large amount of memory and multiple CPUs.
The AM server is configured to use CTS-based sessions.
The following table summarizes the high-level tasks required to tune an AM instance:
| Task | Resources |
|---|---|
| Tune General AM Settings | |
| Tune Connectivity to LDAP Data Stores | |
| Tune the JVM where AM Runs | |
| Tune the Configuration and User Caches | "Tuning Caching" |