The PingDirectory server provides an entry cache implementation, which allows for fine-grained control over entries that are held in the cache.
You can define filters to specify the entries included in or excluded from the cache, and you can restrict the cache so that it holds only entries with at least a specified number of values for a given set of attributes.
For most circumstances, use the PingDirectory server without an entry cache. In most cases, the server efficiently retrieves and decode entries from the database. The database cache is more space-efficient than the entry cache, and heavy churn in the entry cache can adversely impact garbage collection behavior.
Entry caches with large static groups
If the PingDirectory server contains large static groups, such as those containing thousands or millions of members, and clients need to frequently retrieve or otherwise interact with these groups, enable an entry cache that holds only large static groups.
In servers containing large static groups, define an entry cache to hold only those large static groups. To define this entry cache, include a filter that matches only group entries, as shown in the following example.
The filter contains a minimum value count so that only groups with a large number of
members, such as those with at least 100
uniqueMember values are included. By default, the PingDirectory server entry cache implementation with these
settings is disabled. To use this implementation, you must enable these settings.