JVM stack traces must be collected before killing the affected process or restarting the server otherwise the information relating to the affected process is lost forever, which may make it impossible to identify the root cause. One common index issue that contributes to high CPU is unindexed searches see Unindexed searches causing slow searches and poor performance on DS (All versions) server for further information. See How do I troubleshoot issues with my indexes in DS (All versions)? for further information on troubleshooting indexes. The configuration file ( config.ldif, which is located in the /path/to/ds/config directory where DS is installed) contains all the configuration settings for a DS server instance and is useful for checking your configuration, including index settings.

See How do I use the Access log to troubleshoot DS (All versions)? for further information about this log file and advice on resolving common issues identified in the logs. This file is located in the /path/to/ds/logs directory where DS is installed. The Access log file records details about all the operations processed by the server. Please notify us of the exact timestamp when high CPU was noticed so we can focus our attention on the relevant information.

It is necessary to collect the data at the point when the server is exhibiting high CPU so the timestamps across the data set correspond with the time high CPU occurred.

Check cpu usage