Deployment Architecture

Splunk Sizing

sidtalup27
Explorer

Hello,

We are sizing a Splunk solution for internal usage. Referring to the documentation, it is said that Mid size Indexer will require 48vCPU and 64Gb RAM. However, I wanted to understand how much EPS will this kind of indexer handle.

Please advise

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

That size node should work well for most cases. As @johnhuang said, in pure splunk indexing it should manage 300Gb/d. Then if you have e.g. ES or ITSI then it’s different story.

EPS is dependent of your event size, complexity and what your want to do with them. We should separate EPS for ingestion and search time as those are totally different cases.  Also you should ensure that your storage has at least 800+ (preferred 1200+) IOPS to move data in and out enough quickly. There are couple of tools like Bonnie or fio which you could use to check that.

t. Ismo

0 Karma

johnhuang
Motivator

Here's the sizing recommendation from Splunk: Capacity Planning Manual - Summary of performance recommendations. Your hardware spec should comfortably handle 300GB/day.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...