Memory and stats search performance
A pair of limits.conf
settings strike a balance between the performance of the stats
family of search commands and the amount of memory they use during the search process, in RAM and on disk. If your stats
, sistats
, geostats
, tstats
, or mstats
searches are consistently slow to complete, you can adjust these settings to improve their performance, but at the cost of increased search-time memory usage, which can lead to search failures.
When you run a stats
search, the search head returns batches of results until the search result set is complete. The max_mem_usage_mb
setting in the [default]
stanza of limits.conf
limits the amount of memory (RAM) that a batch of search results can take up during the stats
search process. Its default setting is 200 MB. Lower limits to max_mem_usage_mb
can cause a search to be slower to complete, but there should be no loss of results.
The stats
command processor spills data from RAM to disk when the amount of RAM that the batch is estimated to use exceeds max_mem_usage_mb
. Do not set max_mem_usage_mb=0
as this removes the bounds to the amount of memory a batch can use.
If you run a lot of high cardinality stats
searches (searches that must match, filter, and aggregate extremely large numbers of discrete field values), consider reducing max_keymap_rows
to improve their performance. This setting in the [stats | sistats]
stanza of limits.conf
limits the number of result rows that the stats
search processor can store in the key map during the mapping phase of the map-reduce operation in a stats
search. The stats
search processor stores expunged result rows in memory, subject to the max_mem_usage_mb
setting.
The eventstats
and streamstats
commands also use these settings, but in a slightly different way.
For more information, see the topics for eventstats
and streamstats
in the Search Reference.
- Splunk Cloud Platform
- To change these limitations, request help from Splunk Support. If you have a support contract, file a new case using the Splunk Support Portal at Support and Services. Otherwise, contact Splunk Customer Support.
- Splunk Enterprise
- Prerequisites
- Only users with file system access, such as system administrators, can increase the
max_mem_usage_mb
andmax_keymap_rows
settings using configuration files. - Review the steps in How to edit a configuration file in the Splunk Enterprise Admin Manual.
- Only users with file system access, such as system administrators, can increase the
Never change or copy the configuration files in the default directory. The files in the default directory must remain intact and in their original location. Make the changes in the local directory.
- Steps
- Open the local
limits.conf
file for the Search app. For example,$SPLUNK_HOME/etc/apps/<app_name>/local
. - Under the [default] stanza, set
max_mem_usage_mb
to the value you want to use. - Under the [stats | sistats] stanza, set
max_keymap_rows
to the value you want to use.
Add sparklines to search results | About advanced statistics |
This documentation applies to the following versions of Splunk Cloud Platform™: 9.2.2406, 8.2.2201, 8.2.2202, 8.2.2203, 9.0.2205, 9.0.2208, 9.0.2209, 9.0.2303, 9.0.2305, 9.1.2308, 9.1.2312, 9.2.2403 (latest FedRAMP release), 8.2.2112
Feedback submitted, thanks!