<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why does the table command in Splunk cause performance degradation? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364223#M107510</link>
    <description>&lt;P&gt;Please share your full query.  The &lt;CODE&gt;table&lt;/CODE&gt; command by itself usually is not a performance drag.&lt;/P&gt;</description>
    <pubDate>Sun, 13 Aug 2017 17:01:10 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2017-08-13T17:01:10Z</dc:date>
    <item>
      <title>Why does the table command in Splunk cause performance degradation?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364222#M107509</link>
      <description>&lt;P&gt;When I use this command ( table ) it runs at a slow speed .... please help me.&lt;BR /&gt;
Thank you for your answer.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Aug 2017 06:36:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364222#M107509</guid>
      <dc:creator>splunk_anoosheh</dc:creator>
      <dc:date>2017-08-13T06:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why does the table command in Splunk cause performance degradation?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364223#M107510</link>
      <description>&lt;P&gt;Please share your full query.  The &lt;CODE&gt;table&lt;/CODE&gt; command by itself usually is not a performance drag.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Aug 2017 17:01:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364223#M107510</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2017-08-13T17:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why does the table command in Splunk cause performance degradation?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364224#M107511</link>
      <description>&lt;P&gt;Oh, this one killed me for a while. &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;fields&lt;/CODE&gt; is a streaming, distributable command.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;table&lt;/CODE&gt; is neither.  &lt;CODE&gt;table&lt;/CODE&gt;, 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 &lt;CODE&gt;table&lt;/CODE&gt; cannot run until all the results are returned to the search head, whereas &lt;CODE&gt;fields&lt;/CODE&gt; can be run at each indexer.&lt;/P&gt;

&lt;P&gt;So, use &lt;CODE&gt;fields&lt;/CODE&gt; if you are up in the area where you are dealing with streaming distributable commands, and only use &lt;CODE&gt;table&lt;/CODE&gt; later, after everything is already on the search head.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2017 14:16:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-does-the-table-command-in-Splunk-cause-performance/m-p/364224#M107511</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-08-14T14:16:34Z</dc:date>
    </item>
  </channel>
</rss>

