<?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: How do I deal with performance issues using the transaction command with a large amount of data? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265122#M79686</link>
    <description>&lt;P&gt;I find it helps to visualise Splunk as a single giant database table with unlimited columns. So in fact your events are already "joined" and all you need to do is group statistics together in a meaningful way.&lt;/P&gt;

&lt;P&gt;Assuming each mID,jID pair is unique, you can group all you fields together like so&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=performance (source=subtask OR source=maintask ) | stats values(*) AS * by mID,jID
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should give you a table of all the fields that belong to each mID jID pair. The fields will be multivalued, so you may need to split them with mvexpand&lt;/P&gt;

&lt;P&gt;There is a great flowchart on when you use each aggregation command here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/Search/Abouteventcorrelation"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/Search/Abouteventcorrelation&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See Stats: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Stats"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Stats&lt;/A&gt; &lt;BR /&gt;
See Mvexpand: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Mvexpand"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Mvexpand&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Feb 2016 10:41:34 GMT</pubDate>
    <dc:creator>jplumsdaine22</dc:creator>
    <dc:date>2016-02-05T10:41:34Z</dc:date>
    <item>
      <title>How do I deal with performance issues using the transaction command with a large amount of data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265119#M79683</link>
      <description>&lt;P&gt;I have a new application that I need to extract one field, &lt;STRONG&gt;taskname&lt;/STRONG&gt;, from the main task table (5+ million records) and merge into the subtask table (less 1 million records).  When I ran with the 'transaction' statement, I got incomplete results.&lt;/P&gt;

&lt;P&gt;Here are my file structures.  One main task will have multiple subtasks and each subtask might run in serialized or parallel.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Main  taskA (mID, jID, mCPU, taskname, main task beginning/ending time)
  subtask1: mID, jID, sCPU, subtask beginning/ending time  
  subtask2: mID, jID, sCPU, subtask beginning/ending time 
  . . . . .
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I need to search each detailed subtask attributes by task name across different time frame.  And, another search will be summarized by time distribution.  I know the later one can be achieved with &lt;CODE&gt;| timechart sum(sCPU) by taskname span=1h&lt;/CODE&gt;.  But, I got the performance issue for the first search.  I did search to use summary indexing and post processing. It seems they suggest to aggregate fields mID and jID.  However, I will lose the subtask detailed information.  Any suggestion?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2016 01:29:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265119#M79683</guid>
      <dc:creator>jlo</dc:creator>
      <dc:date>2016-02-03T01:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: How do I deal with performance issues using the transaction command with a large amount of data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265120#M79684</link>
      <description>&lt;P&gt;Can you post the query with &lt;CODE&gt;transaction&lt;/CODE&gt; command that you are using?&lt;BR /&gt;
Is your main task table and subtask table are different files?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2016 05:01:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265120#M79684</guid>
      <dc:creator>Murali2888</dc:creator>
      <dc:date>2016-02-03T05:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: How do I deal with performance issues using the transaction command with a large amount of data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265121#M79685</link>
      <description>&lt;P&gt;the base search,&lt;/P&gt;

&lt;P&gt;index=performance source=subtask OR source=maintask &lt;BR /&gt;
| transaction mID jID  startswith=(source="subtask") endswith=(source="maintask")&lt;/P&gt;

&lt;P&gt;....&lt;/P&gt;

&lt;P&gt;use the search base for the query1&lt;/P&gt;

&lt;P&gt;| timechart sum(sCPU) by taskname span=1h&lt;/P&gt;

&lt;P&gt;....&lt;/P&gt;

&lt;P&gt;use the search base for the query2&lt;/P&gt;

&lt;P&gt;| table mID jID sCPU taskname sATT1 sATT2 sATT3&lt;BR /&gt;
| sort 0 -sCPU | head 100&lt;/P&gt;

&lt;P&gt;where sATTx are minor test attributes from the source=subtask; and taskname is from source=maintask.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2016 06:45:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265121#M79685</guid>
      <dc:creator>jlo</dc:creator>
      <dc:date>2016-02-03T06:45:02Z</dc:date>
    </item>
    <item>
      <title>Re: How do I deal with performance issues using the transaction command with a large amount of data?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265122#M79686</link>
      <description>&lt;P&gt;I find it helps to visualise Splunk as a single giant database table with unlimited columns. So in fact your events are already "joined" and all you need to do is group statistics together in a meaningful way.&lt;/P&gt;

&lt;P&gt;Assuming each mID,jID pair is unique, you can group all you fields together like so&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=performance (source=subtask OR source=maintask ) | stats values(*) AS * by mID,jID
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should give you a table of all the fields that belong to each mID jID pair. The fields will be multivalued, so you may need to split them with mvexpand&lt;/P&gt;

&lt;P&gt;There is a great flowchart on when you use each aggregation command here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/Search/Abouteventcorrelation"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/Search/Abouteventcorrelation&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See Stats: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Stats"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Stats&lt;/A&gt; &lt;BR /&gt;
See Mvexpand: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Mvexpand"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Mvexpand&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Feb 2016 10:41:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-deal-with-performance-issues-using-the-transaction/m-p/265122#M79686</guid>
      <dc:creator>jplumsdaine22</dc:creator>
      <dc:date>2016-02-05T10:41:34Z</dc:date>
    </item>
  </channel>
</rss>

