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 you run the import-ldif tool.

If the amount of data that needs to be stored exceeds the available memory capacity of the individual systems on which the server runs, there are a couple options:

  • Break up the data into segments that are small enough to be fully cached on their own, and use PingDirectoryProxy server's entry balancing functionality to make them appear as a single logical set.
  • Tune the server so that the most frequently accessed information can be served from memory while disk access might be required for other data. In disk-bound deployments, you can use backend configuration options such as cache mode, uncached attribute criteria, and uncached entry criteria to help prioritize what data should remain in memory versus what can be retrieved from disk.