Sun Java System Calendar Server 6.3 Administration Guide

21.5 Improving Performance of the LDAP Data Cache

With the LDAP data cache enabled, you can tune it using the ics.conf parameters, adjust one or more of the parameters found in the following table.

Note –

The LDAP data cache is enabled by default. You can disable it by setting: local.ldap.cache.enable="no"

Table 21–1 ics.conf Parameters Used to Customize LDAP Data Caching





The number of seconds for the checkpoint thread to sleep between checkpoints. The default is “60”.

In a high activity LDAP, you might want to decrease the interval to keep the cache as current as possible. At the same time, remember that the more often you refresh the cache, the more system overhead you introduce. 



Specifies whether to remove the LDAP data cache database log files after they have been processed. The default is “yes”.

Do not change this parameter unless you have a custom clean up routine that will remove the old log files. 



Specifies the maximum size in megabytes of checkpoint file. The default is "10” megabytes.

If you have a high activity LDAP, this file could fill up before the checkpoint interval is over. Try to set the value to a number that is close to the actual size of the logs according to your experience 



Specifies the maximum number of threads for the LDAP data cache database. The default is “1000”.

In a high activity LDAP, you might want to increase the number of threads. This could cause increased CPU utilization. Decrease the number of threads only if your LDAP activity is minimal. 



Specifies the number of megabytes of shared memory. The default is “4” megabytes.



Specifies the “time to live” (TTL) in seconds for an LDAP data cache entry. The default is “3600” seconds (1 hour).

If your cache is filling up too fast (high activity), you can decrease the TTL time. However, this could increase the overall number of LDAP database accesses, which could slow the system down overall. 



Specifies the interval in seconds between each cache database cleanup. The default is “1800” seconds (30 minutes).

The system removes expired entries. The time interval does not have to be the same as the entry TTL time. But synchronizing them can make it more efficient. 



Specifies whether or not to log the access to the LDAP data cache and to print statistics in the log file. The default is “no”.

For performance enhancement, use this only in debug mode. 



Specifies the interval in seconds when each statistics report is written to the log file. The default is “1800” seconds (30 minutes).

This is only active if local.ldap.cache.stat.enable is enabled. Decreasing the interval can help you pinpoint problems. Increasing the interval helps decrease system load.

Note –

Communications Express expects data caching to be disabled.