
Optimize indexes
While the indexer is indexing data, one or more instances of the splunk-optimize
process will run intermittently, merging index files together to optimize performance when searching the data. The splunk-optimize
process can use a significant amount of cpu but only briefly. You can reduce the number of concurrent instances of splunk-optimize
by changing the value of maxConcurrentOptimizes
in indexes.conf
, but this is not typically necessary.
If splunk-optimize
does not run frequently enough, searching will be less efficient.
splunk-optimize
runs only on hot buckets. You can run it on warm buckets manually, if you find one with a larger number of index (.tsidx
) files; typically, more than 25. To run splunk-optimize
, go to $SPLUNKHOME/bin
and type:
splunk-optimize -d|--directory <bucket_directory>
splunk-optimize
accepts a number of optional parameters. To see a list of available parameters, type:
splunk-optimize
For more information on buckets, see How Splunk stores indexes.
PREVIOUS Manage pipeline sets for index parallelization |
NEXT Use the DMC to view indexing performance |
This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14, 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11, 6.2.12, 6.2.13, 6.2.14, 6.2.15, 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10
Feedback submitted, thanks!