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!

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...