<?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: Initial stage of Splunk performance tunning in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306629#M67304</link>
    <description>&lt;P&gt;Splunk cares more about CPU cores than memory. A rule of thumb is each concurrent search represents approx 1 CPU core. This is configurable though&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.4/Deploy/Referencehardware"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.4/Deploy/Referencehardware&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 26 Aug 2017 21:30:06 GMT</pubDate>
    <dc:creator>skoelpin</dc:creator>
    <dc:date>2017-08-26T21:30:06Z</dc:date>
    <item>
      <title>Initial stage of Splunk performance tunning</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306626#M67301</link>
      <description>&lt;P&gt;We have deployed our splunk in our organization. We are currently ingesting 1.7 TB data per day and it can increase up to 3.5 TB. We are using high performance hardware resources for splunk.&lt;BR /&gt;
Now I would like to know what would be the better tuning memory parameters  which need to set for SH/Indexer to increase the performance? Otherthan memory do we need to look into any other settings?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Aug 2017 16:11:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306626#M67301</guid>
      <dc:creator>rreddy012c</dc:creator>
      <dc:date>2017-08-26T16:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Initial stage of Splunk performance tunning</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306627#M67302</link>
      <description>&lt;P&gt;Depending on the specs of your indexers, you could enable parallelization to increase throughput &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.3/Capacity/Parallelization"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.3/Capacity/Parallelization&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Aug 2017 18:21:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306627#M67302</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2017-08-26T18:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: Initial stage of Splunk performance tunning</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306628#M67303</link>
      <description>&lt;P&gt;Thanks for suggestion and How memory does splunk allocates for each search?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Aug 2017 18:50:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306628#M67303</guid>
      <dc:creator>rreddy012c</dc:creator>
      <dc:date>2017-08-26T18:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Initial stage of Splunk performance tunning</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306629#M67304</link>
      <description>&lt;P&gt;Splunk cares more about CPU cores than memory. A rule of thumb is each concurrent search represents approx 1 CPU core. This is configurable though&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.4/Deploy/Referencehardware"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.4/Deploy/Referencehardware&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Aug 2017 21:30:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306629#M67304</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2017-08-26T21:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: Initial stage of Splunk performance tunning</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306630#M67305</link>
      <description>&lt;P&gt;Many many aspects are involved. The following can assist - &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.2/Admin/OptimizeSplunkforpeakperformance"&gt;Optimize Splunk for peak performance&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 27 Aug 2017 01:44:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Initial-stage-of-Splunk-performance-tunning/m-p/306630#M67305</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2017-08-27T01:44:59Z</dc:date>
    </item>
  </channel>
</rss>

