Deployment Architecture

Distributed search sizing

ontai
Explorer

I've looked through some of the documentation for separating search heads from indexers depending on the number of concurrent searches and users. I'm wondering what a rough idea of the architecture and hardware requirements would look like to support:

10-20 GB per day
20 concurrent users
10 concurrent saved searches

Thanks.

Craig

Tags (1)
0 Karma

araitz
Splunk Employee
Splunk Employee

Given your user and scheduler concurrency, you would probably be best off implementing an indexer and a search head. Although you can easily index 80-100 GB/day on a single commodity server, having 20 concurrent users and 10+ concurrent scheduled searches on the same machine wouldn't allow for the best user experience or much room for growth.

0 Karma

Takajian
Builder

I agree your suggestion. This is appropriate sizing with considering to future plan. My answer was rough idea.

0 Karma

Takajian
Builder

I do not think you do not need dedicated search head when you index data less than 100GB per day on one box server. You can also refer to following site. Hope this help.

http://docs.splunk.com/Documentation/Splunk/latest/installation/capacityplanningforalargersplunkdepl...

0 Karma
Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...