Splunk® Enterprise

Installation Manual

Download manual as PDF

Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

How saved searches affect Splunk Enterprise performance

This topic discusses how the number of saved searches - searches that you save to use again at a later time - affect performance in Splunk Enterprise.

On a reference indexer, a saved search consumes about 1 CPU core and a specified amount of memory while it executes. It also increases the amount of disk I/O temporarily as the disk subsystem looks through the indexes to fetch the desired data.

Each additional saved search that executes at the same time consumes an additional CPU core. This consumption is separate from CPU usage from the operating system and Splunk Enterprise indexing and storage processes.

If more saved searches execute than can be accepted for processing, they will queue. Splunk Enterprise also warns you when the system reaches the maximum number of saved searches. When searches queue, search results return more slowly.

Adding indexers and search heads provides additional CPU cores to run more concurrent searches. Adding RAM to your existing machines helps with concurrent searches but does not give you additional search capacity.

Last modified on 15 July, 2014
How the number of concurrent users impacts Splunk Enterprise performance
How search types impact Splunk Enterprise 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

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters