If you set a limit of 70% of your searches to be scheduled searches, ad-hoc searches may run more slowly.When you configure limits, be sure to first test your settings in a test environment to ensure they are optimal for your production environment. Concurrency limits are replicated between search head cluster members.įor more information about the Experience designations, see Determine your Splunk Cloud Platform Experience. If your Splunk Cloud Platform deployment is on the Classic Experience and a search head cluster, you must click Show All Settings for server settings to be available.
If your Splunk Cloud Platform deployment is on the Victoria Experience, you can configure concurrency limits for both search heads and search head clusters.You must have the edit_search_concurrency_all and edit_search_concurrency_scheduled capabilities to configure these settings.Before adjusting these concurrency limits, note the following: You can adjust limits for concurrent scheduled searches and summarization searches in Splunk Web using the Settings > Server settings > Search preferences page. If you use primarily data model acceleration searches, consider allocating a larger percentage of searches to summarization searches.If you primarily run scheduled searches, consider making most of your searches scheduled searches.You can adjust the relative number of concurrent scheduled and summarization searches to meet the needs of your organization. 25% of your concurrent searches are summarization searches.50% of your concurrent searches are scheduled searches.In Splunk Cloud Platform, this concurrent limit is configured for you. When you run searches, Splunk limits the number of concurrent searches to preserve the performance for each search.
Set limits for concurrent scheduled searches
0 kommentar(er)
