Splunk Search

Why does the table command in Splunk cause performance degradation?

splunk_anoosheh
New Member

When I use this command ( table ) it runs at a slow speed .... please help me.
Thank you for your answer.

0 Karma

DalJeanis
Legend

Oh, this one killed me for a while.

fields is a streaming, distributable command.

table is neither. table, as well as dropping all non-mentioned fields, reformats the data internally, and limits the results as per some system parameters. It may do other stuff, but the bottom line is that table cannot run until all the results are returned to the search head, whereas fields can be run at each indexer.

So, use fields if you are up in the area where you are dealing with streaming distributable commands, and only use table later, after everything is already on the search head.

richgalloway
SplunkTrust
SplunkTrust

Please share your full query. The table command by itself usually is not a performance drag.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Reuse: Word-play

This puzzle series (first published here) is based on analysing words.Some of the statements in your puzzle ...

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...