You can configure the PingDirectory server for a disk-bound configuration.
For best performance, configure the server to fully cache the DIT in the backend database cache. The server configuration assumes this scenario. For databases too large to fit in memory, other options are available:
- Configure the server for a disk-bound data set. When the database is stored on an SSD, this configuration yields server performance that is comparable to a fully-cached scenario.
- Use uncached attributes or entries as described in the following section.
- Use a PingDirectoryProxy server in an entry-balancing deployment, which allows all data to be cached in a partitioned environment.
- When installing the server, choose the Aggressive option for JVM memory configuration and to preload the data when the server starts.
Set operating system
vm.swappinessto 0 to protect the server JVM process from an overly aggressive file system cache.
When the data set is imported with the above settings, verify in the
import-ldifoutput that the cached portions of the data set fit comfortably within the database cache.