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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...