Deployment Architecture

Are there performance issues for increasing the "max_searches_per_CPU" setting in limits.conf to accommodate more historical concurrent searches?


I have 16 core CPU on search head which accommodate 22 concurrent searches by default. When 22 concurrent searches is reached, it shows limit has been reached, but the CPU utilization is only 20 percent.

Can we increase the max_searches_per_CPU=2 or 3 in order to accommodate more historical concurrent searches. Does this have any performance issues?

Why does Splunk have default value=1?

0 Karma


If your system can handle the load, you can increase your max_searches_per_cpu. I had an old instance where we had it at 6 on search heads with 12 core CPUs.

0 Karma
Take the 2021 Splunk Career Survey

Help us learn about how Splunk has
impacted your career by taking the 2021 Splunk Career Survey.

Earn $50 in Amazon cash!