Best performance is achieved when the contents of the database can be fully cached in memory. If possible, the amount of memory allocated to PingDirectory Server should be large enough so that all of the data can fit in the database cache. Memory sizing estimates appear at the end of the output when the import-ldif tool is run.

If the amount of data that needs to be stored exceeds the available memory capacity of the individual systems on which the server will run, there are several options:
  • You can break up the data into segments that are small enough to be fully cached on their own, and usePingDirectoryProxy Server’s entry balancing functionality to make them appear as a single logical set.
  • You can tune the server so that the most-frequently accessed information can be served from memory while disk access may be required for other data. In disk-bound deployments, backend configuration options such as cache mode, uncached attribute criteria, and uncached entry criteria can be used to help prioritize what data should remain in memory versus what may be retrieved from disk.