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!

Splunk Security Content for Threat Detection & Response, Q1 Roundup

Join Principal Threat Researcher, Michael Haag, as he walks through:An introduction to the Splunk Threat ...

Splunk Life | Happy Pride Month!

Happy Pride Month, Splunk Community! 🌈 In the United States, as well as many countries around the ...

SplunkTrust | Where Are They Now - Michael Uschmann

The Background Five years ago, Splunk published several videos showcasing members of the SplunkTrust to share ...