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!

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had 3 releases of new security content via the Enterprise Security ...

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...