Lightweight Directory Access Protocol performance settings
Use this page to minimize impacts to performance by adding opened connections and contexts to internally maintained pools and reusing them. Also minimize performance impacts by maintaining internal caches of retrieved data.
- In the administrative console, click .
- Under User account repository, select Federated repositories from the Available realm definitions field and click Configure. To configure for a specific domain in a multiple security domain environment, click . Under Security Attributes, expand User Realm, and click Customize for this domain. Select the Realm type as Federated repositories and then click Configure.
- Under Related items, click Manage repositories.
- Click Add to specify a new external repository or select an external repository that is preconfigured.
- Under Additional properties, click Performance.
When you finish adding or updating your federated repository configuration, go to the Apply to validate the changes.
panel and clickLimit search time
Specifies the timeout value in milliseconds for a Lightweight Directory Access Protocol (LDAP) server to respond before stopping a request.
Information | Value |
---|---|
Data type: | Integer |
Units: | Milliseconds |
Default: | 0 |
Range: | Equal to or greater than 0. A value of 0 specifies that no search time limit exists. |
Limit search returns
Specifies the maximum number of entries that are returned in a search result.
Information | Value |
---|---|
Data type: | Integer |
Units: | Entries |
Default: | 0 |
Range: | Equal to or greater than 0. A value of 0 specifies that no search return limit exists. |
Use connection pooling
Specifies whether to utilize the connection pooling function, which is provided in the Software Development Kit (SDK).
Connection pooling is maintained by the Java™ run time. It is configured by system properties.
Information | Value |
---|---|
Default: | Disabled |
Range: | Enabled or Disabled |
Enable context pool
Specifies whether context pooling is enabled to the LDAP server. To improve performance, use the context pool in combination with connection pooling.
Information | Value |
---|---|
Default: | Enabled |
Range: | Enabled or Disabled |
Initial size
Specifies the number of context instances in the pool when the pool is initially created by the LDAP repository.
Information | Value |
---|---|
Data type: | Integer |
Default: | 1 |
Range: | 1 to 50 |
Preferred size
Specifies the preferred number of context instances that the context pool maintains. Both in-use and idle context instances contribute to this number.
Information | Value |
---|---|
Data type: | Integer |
Default: | 3 |
Range: | 0 to 100 |
Maximum size
Specifies the maximum number of context instances that can be maintained concurrently by the context pool. Both in-use and idle context instances contribute to this number.
When the pool size reaches the maximum size, no new context instances can be created for a new request. The new request is blocked until a context instance is released or removed. The request periodically checks for context instances that are available in the pool. A request for a pooled context instance uses an existing pooled and idle context instance or a newly created pooled context instance.
A maximum pool size of 0 indicates that the context pool can maintain an infinite number of context instances.
Information | Value |
---|---|
Data type: | Integer |
Default: | 0 |
Context pool times out
Specifies the number of seconds for the context pool to time out and remove idle context instances.
A timeout value of 0 indicates that the context pool does not time out context instances.
Information | Value |
---|---|
Data type: | Integer |
Default: | 0 |
Cache the attributes
Specifies whether to cache the attributes that are returned from the LDAP server.
Information | Value |
---|---|
Default: | Enabled |
Range: | Enabled or Disabled |
Cache size
Specifies the maximum size of the cache.
Information | Value |
---|---|
Data type: | Integer |
Default: | 4000 |
Range: | Equal to or greater than 100 |
Cache times out
Specifies the maximum number of seconds that the cached search results can stay in the cache.
A timeout value of 0 indicates that the cached search results stay in the cache until update operations are made.
Information | Value |
---|---|
Data type: | Integer |
Units: | Seconds |
Default: | 1200 |
Range: | Equal to or greater than 0 |
Distribution policy
Specifies the distribution policy for the cache in a clustered environment, which is one of the following:
- Not shared
- Sends out new entries, both ID and data, and updates to those entries.
- Push
- Requests data from other servers in the cluster when that data is not locally present.
- Push and pull
- Sends out IDs for new entries and requests from other servers in the cluster entries for IDs that were previously broadcast. The dynamic cache always sends out cache entry invalidations.
Cache the search results
Specifies whether to cache the search results that are returned from the LDAP server.
Information | Value |
---|---|
Default: | Enabled |
Range: | Enabled or Disabled |
Cache size
Specifies the maximum size of the cache.
Information | Value |
---|---|
Data type: | Integer |
Default: | 2000 |
Range: | Equal to or greater than 100 |
Cache times out
Specifies the maximum number of seconds that the cached search results can stay in the cache.
A timeout value of 0 indicates that the cached search results stay in the cache until update operations are made.
Information | Value |
---|---|
Data type: | Integer |
Units: | Seconds |
Default: | 600 |
Range: | Equal to or greater than 0 |
Distribution policy
Specifies the distribution policy for the cache in a clustered environment, which is one of the following:
- Not shared
- Sends out new entries, both ID and data, and updates to those entries.
- Push
- Requests data from other servers in the cluster when that data is not locally present.
- Push and pull
- Sends out IDs for new entries and requests from other servers in the cluster entries for IDs that were previously broadcast. The dynamic cache always sends out cache entry invalidations.