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!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...