Splunk Search

Where is the bottleneck?

rmcdougal
Path Finder

We are having minor performance issues with our deployment and I would like an outside opinion on where the bottleneck might be. Our current deployment looks like this;

Splunk 5.0.1

2 Search Heads - Virtual; 4 CPU Cores Each; 6 GB RAM

1 Master Node - Virtual; 2 CPU Cores; 4 GB RAM;

2 Indexers - Physical; 24 CPU Cores; 24 GB RAM; 350 IOPS per server

I suspect the biggest issue is the number of CPU cores on the search heads, does anyone see another constraint I have missed?

Tags (1)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Your indexer IOPS is fairly low, their cores likely are bored to death.

The number of cores on the search heads will limit the number of searches you can run concurrently, indeed.

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk, and empower your SOC to reach new heights! Duration: 1 hour  Prepare to ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...