Splunk Search

Why is stats more efficient and better supported with MapReduce than transaction?

kj384g
New Member

I was told that stats is more efficent and better supported with MapReduce... is that true and if so why?

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

The two don't do the same thing.

stats usually does less, so it'll be faster than transaction which is doing more work. For example, transaction will build multi-value fields for you while stats only builds those fields you specify.

As for using MapReduce more efficiently, grouping events together with transaction requires knowing all the events in one place - the search head. stats has less complex features - e.g. no maxspan, maxpause, non-unique identifiers - that allow a lot of work to be done on the indexers.

To sum up, if stats does what you need then it'll be faster almost every time.

0 Karma
Get Updates on the Splunk Community!

Streamline Data Ingestion With Deployment Server Essentials

REGISTER NOW!Every day the list of sources Admins are responsible for gets bigger and bigger, often making the ...

Remediate Threats Faster and Simplify Investigations With Splunk Enterprise Security ...

REGISTER NOW!Join us for a Tech Talk around our latest release of Splunk Enterprise Security 7.2! We’ll walk ...

Introduction to Splunk AI

WATCH NOWHow are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. ...