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
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.
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
streamstats commands also use these settings, but in a slightly different way.
- Only users with file system access, such as system administrators, can increase the
max_keymap_rowssettings using configuration files.
- Review the steps in How to edit a configuration file in the Splunk Enterprise Admin Manual.
- You can have configuration files with the same name in your default, local, and app directories. Read Where you can place (or find) your modified configuration files in the Splunk Enterprise Admin Manual.
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 changes to the files in the local directory.
If you are using Splunk Cloud and want to change either of these limits, file a Support ticket.
Add sparklines to search results
About advanced statistics
This documentation applies to the following versions of Splunk Cloud Platform™: 8.1.2009, 8.1.2011, 8.1.2012, 8.1.2101, 8.1.2103, 8.2.2104, 8.2.2105 (latest FedRAMP release), 8.2.2106, 8.2.2107