<?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: multireport vs. appendpipe in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/multireport-vs-appendpipe/m-p/558911#M9302</link>
    <description>&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Update to the appendpipe version of code&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;I eliminated stanza2 and the final aggregation SPL reducing the overall code to just the&amp;nbsp;&lt;SPAN&gt;pre-appendpipe SPL and stanza 1 but leaving the appendpipe nomenclature in the code.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Total execution time = 486 sec&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then for this exact same search, I eliminated the appendpipe&amp;nbsp; syntax.&amp;nbsp;Everything is the same except for the&amp;nbsp; | appendpipe and [ ] syntax.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Total execution time = 77 sec&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The overhead to using appendpipe is HUGE.&lt;/P&gt;&lt;P&gt;I suspect the same is true for using multireport.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jul 2021 21:24:16 GMT</pubDate>
    <dc:creator>actionabledata</dc:creator>
    <dc:date>2021-07-09T21:24:16Z</dc:date>
    <item>
      <title>multireport vs. appendpipe</title>
      <link>https://community.splunk.com/t5/Reporting/multireport-vs-appendpipe/m-p/558909#M9301</link>
      <description>&lt;P&gt;Code Architecture:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;common code generating initial results; generate unique key for each grouping&lt;/LI&gt;&lt;LI&gt;multireport or appendpipe&amp;nbsp;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;stanza 1 with its own set of stats, evals, etc.; uses the key from the common code&lt;/LI&gt;&lt;LI&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;stanza 2 with its own set of stats, evals, etc.; uses the key from the common code&lt;/LI&gt;&lt;LI&gt;Aggregates the resulting data from the common, stanza1, stanza2 results using the key&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Issue Statement&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;common code + stanza 1 takes about 1 min to execute&lt;/LI&gt;&lt;LI&gt;common code + stanza 2 takes about 1 min to execute&lt;/LI&gt;&lt;LI&gt;common code + stanza 1 + stanza2 using either a multireport or appendpipe takes about 17 min&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;[Q] Does this huge execution time difference make sense?&lt;/P&gt;&lt;P&gt;I have attached a few images to show how I think&amp;nbsp;multireport and appendpipe work.&lt;/P&gt;&lt;P&gt;[Q] Is my understanding accurate?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="50%"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="actionabledata_0-1625861746744.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/15014i7A114DE7C1A27465/image-size/medium?v=v2&amp;amp;px=400" role="button" title="actionabledata_0-1625861746744.png" alt="actionabledata_0-1625861746744.png" /&gt;&lt;/span&gt;&lt;/TD&gt;&lt;TD width="50%"&gt;&lt;P&gt;The&amp;nbsp;pre-appendpipe SPL reads the data from the index, filters the data, creates some initial fields using streamstats and eventstats and creates a key that is unique per the overall groupings correlated within this code.&lt;BR /&gt;&lt;BR /&gt;Lines 1 and 2 are identical and originate from the pre-multireport SPL. These results are presented to the stanza1 and stanza2 SPL.&lt;/P&gt;&lt;P&gt;Lines 3 and 4 are independent results from stanza1 and stanza2 respectively&lt;/P&gt;&lt;P&gt;stanza1 and stanza2 execute mutually exclusive from one another&lt;/P&gt;&lt;P&gt;The sort and stats clauses within stanza1 and stanza2 are quite different but the one does NOT impact the other.&lt;/P&gt;&lt;P&gt;The final aggregation software ties all the data together based on a common key.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="50%"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="actionabledata_1-1625861773920.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/15015i38D1E0F89016CFBF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="actionabledata_1-1625861773920.png" alt="actionabledata_1-1625861773920.png" /&gt;&lt;/span&gt;&lt;/TD&gt;&lt;TD width="50%"&gt;&lt;P&gt;The&amp;nbsp;pre-appendpipe SPL reads the data from the index, filters the data, creates some initial fields using streamstats and eventstats and creates a key that is unique per the overall groupings correlated within this code.&lt;BR /&gt;&lt;BR /&gt;Lines 1 and 2 and 3 are identical and originate from the pre-appendpipe SPL. These results are presented to the stanza1 and stanza2 SPL.&lt;/P&gt;&lt;P&gt;Lines 3 and 4 CAN be removed if I filter the input data with a where clause and the flag I called "which" associated with each set of data.&lt;/P&gt;&lt;P&gt;Lines 5 and 6 are independent results from stanza1 and stanza2 respectively&lt;/P&gt;&lt;P&gt;stanza1 and stanza2 execute mutually exclusive from one another.&lt;/P&gt;&lt;P&gt;The stats clauses within stanza1 and stanza2 are quite different but the one does NOT impact the other.&lt;/P&gt;&lt;P&gt;The final aggregation software ties all the data together based on a common key.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 20:31:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/multireport-vs-appendpipe/m-p/558909#M9301</guid>
      <dc:creator>actionabledata</dc:creator>
      <dc:date>2021-07-09T20:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: multireport vs. appendpipe</title>
      <link>https://community.splunk.com/t5/Reporting/multireport-vs-appendpipe/m-p/558911#M9302</link>
      <description>&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Update to the appendpipe version of code&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;I eliminated stanza2 and the final aggregation SPL reducing the overall code to just the&amp;nbsp;&lt;SPAN&gt;pre-appendpipe SPL and stanza 1 but leaving the appendpipe nomenclature in the code.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Total execution time = 486 sec&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then for this exact same search, I eliminated the appendpipe&amp;nbsp; syntax.&amp;nbsp;Everything is the same except for the&amp;nbsp; | appendpipe and [ ] syntax.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Total execution time = 77 sec&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The overhead to using appendpipe is HUGE.&lt;/P&gt;&lt;P&gt;I suspect the same is true for using multireport.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jul 2021 21:24:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/multireport-vs-appendpipe/m-p/558911#M9302</guid>
      <dc:creator>actionabledata</dc:creator>
      <dc:date>2021-07-09T21:24:16Z</dc:date>
    </item>
  </channel>
</rss>

