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!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...